System and method for management of airspace for unmanned aircraft

ABSTRACT

A system and method for management of airspace for unmanned aircraft is disclosed. The system and method comprises administration of the airspace including designation of flyways and zones with reference to features in the region. The system and method comprises administration of aircraft including registration of aircraft and mission. A monitoring system tracks conditions and aircraft traffic in the airspace. Aircraft may be configured to transact with the management system including to obtain rights/priority by license and to operate in the airspace under direction of the system. The system and aircraft may be configured for dynamic transactions (e.g. licensing/routing). The system will set rates for licenses and use/access to the airspace and aircraft will be billed/pay for use/access of the airspace at rates using data from data sources.

FIELD

The present invention relates to a system and method for management ofan airspace for unmanned aircraft. The present invention also relates toa system and method for operation of an unmanned aircraft in anairspace. The present invention further relates to an unmanned aircraftconfigured to operate in an airspace.

CROSS-REFERENCE TO RELATED APPLICATIONS Priority Applications

[None]

Related Applications

(a) U. S. patent application Ser. No. 14/501,343, entitled UNMANNEDAIRCRAFT CONFIGURED FOR OPERATION IN A MANAGED AIRSPACE, naming AlistairK. Chan et al. as inventors, filed Sep. 30, 2014, is related to andincorporated by reference in the present application; (b) U.S. patentapplication Ser. No. 14/501,365, entitled SYSTEM AND METHOD FOROPERATION OF UNMANNED AIRCRAFT WITHIN A MANAGED AIRSPACE, namingAlistair K. Chan et al. as inventors, filed Sep. 30, 2014, is related toand incorporated by reference in the present application.

BACKGROUND

It is well-known to provide a system and method for administration andmanagement of manned aircraft (e.g. with on-board pilot) in an airspace.Systems and methods for air traffic control of manned aircraft such asfor (piloted) commercial flights are very well established in use.Employment of staff such as air traffic controllers to facilitatemanagement of commercial/military flights of manned aircraft operatingin and across airspaces in larger urban areas is well known; air trafficcontrollers interact with on-board pilots of manned aircraft in anairspace and facilitate safe and efficient air traffic in and across theairspace including take-off/landing of aircraft at airports and passageof aircraft through the airspace.

A well-established system of governmental regulation and oversight (e.g.through the U.S. Federal Aviation Administration (FAA)) is in operation.The system of governmental regulation administered by the FAA (and othergovernmental agencies globally) has evolved over many decades to adaptto various changes and advances in technology, aircraft, society, etc.and to events; governmental regulations for air travel are administeredin a generally consistent framework by governmental agencies around theworld such that manned aircraft such as commercial flights are generallyto travel across the country and around the world between most largerurban centers safely and efficiently in accordance with a consistentlyadministrated routine. The air traffic control system now in placeoperates with a relatively exceptional degree of accuracy and efficiencyas indicated by the relatively low number of serious incidents/mishapsthat occur involving manned aircraft safety.

It is also known to use unmanned aircraft (e.g. referred to as unmannedair/aerial vehicle (UAV), unmanned aircraft system (UAS) to include anoperator/pilot at a remote location, drone, etc.). Such unmannedaircraft (UAV/drone craft) at present exist in a wide variety of forms(shapes/sizes), types (e.g. winged craft, rotor-driven craft, etc.),propulsion systems (e.g. engines, thrust-production, etc.), capacities,etc., with a wide variety of capabilities, carrying capacities, controlsystems, telemetry systems, robustness, range, etc., and as exist atpresent are able to perform a wide variety of functions in military,commercial, and recreational applications. At present, the typicalUAV/drone craft is significantly smaller than a typical manned aircraftand may lack the functionality of typical commercial aircraft; someUAV/drone craft have sophisticated on-board control systems; someUAV/drone craft are operated by pilots at remote stations with datacommunications and instrumentation/feedback from the craft; otherUAV/drone craft may have relatively simple control systems (e.g. basicremote control by line of sight by the operator).

The size and form and operation of UAV/drone craft are different fromtypical commercial aircraft and may vary significantly between types ofUAV/drone craft from relatively simple to relatively difficult tocontrol in flight conditions (and in comparison to a typical mannedaircraft). Airworthiness/robustness, controllability/telemetry, datacommunications and failure modes for UAV/drone systems may vary widelybetween UAV/drone craft and in comparison to manned aircraft. Costs tobuild/purchase and operate a UAV/drone system may vary widely betweenUAV/drone craft and in comparison to manned aircraft. UAV/drone craftmay be configured to perform functions for which a manned aircraft isgenerally not suitable (for various reasons) such as local/light parceldelivery, surveillance/monitoring, communications, military/governmentaction, etc. Some UAV/drone craft may be designed as “expendable” or forfinite/one-time use; some UAV/drone craft may be designed forcost-efficiency and simplicity; other UAV/drone systems may be designedfor lengthy useful lives in operation. UAV/drone systems also havegained appeal in a segment of the recreation/hobby/toy industry.

The present trends indicate that the number of UAV/drone systems inexistence/use and the volume of UAV/drone traffic will continue toincrease in the future as forms and functions of UAV/drone systems andmarket uses and acceptance/penetration expands. UAV/drone systemtechnology and capability is likely to continue to advance as willevolution of designs/standards for UAV/drone craft in various categoriesof use.

As the number of UAV/drone systems and the density of UAV/drone trafficincreases so also will increase the need for a safe and efficient systemand method for administration and management of UAV/drone craft in anairspace.

Government regulation of UAV/drone traffic is in an evolutionary phase(as are related jurisdictional/threshold issues) at the present time(e.g. filing date of the present application). It may take several yearsfor an efficient framework to be established for safe and efficientregulation of UAV/drone systems under the FAA and/or agencies of othergovernments. (it is presently uncertain whether the existing frameworkof FAA regulation is well-suited for UAV/drone systems operating inlocal municipalities where local police/law enforcement agencies may bebetter positioned for monitoring/enforcement.) Differences in aircraftas well as in purpose and mission of aircraft may vary materially forthe regulatory framework and enforcement. UAV/drone craft are capable ofoperating in airspaces that differ considerably from airspacesestablished or generally accepted for manned aircraft. Airports and/orterminals for UAV/drone craft may vary widely (e.g. according to needsdictated by the form/type and function of the various UAV/drone craft)from essentially similar to a typical airport to a much smaller base orsimple landing pad.

There is a need for structure and consistency in the administration andmanagement of airspaces for UAV/drone craft as well as for systems andmethods for configuring and operating UAV/drone systems and airspaces,among other reasons, to enhance safe and efficient UAV/drone traffic(e.g. prevent undesired interactions, near-collisions, collisions, etc.between aircraft of all kinds) to facilitate the realization of thepromising potential for productive use of UAV/drone craft in commerceand society.

SUMMARY

Accordingly, it would be advantageous to provide for a system and methodfor management of an airspace for unmanned aircraft. It would also beadvantageous to provide an unmanned aircraft configured for operation ina managed airspace. It would further be advantageous to provide a systemand method for operation of unmanned aircraft in a managed airspacecomprising flyways for unmanned aircraft traffic.

The present invention relates to a system for managing an airspacecomprising a plurality of flyway segments for unmanned aircraftcomprising a computing system configured (1) for administrating theairspace and aircraft and (2) for directing aircraft in the airspace;and a monitoring system configured to monitor conditions in theairspace. The computing system is connected to data sources to providedata for administrating and directing aircraft in the airspace.Administrating the airspace comprises designation of a set of zonescomprising a set of flyway segments in the airspace for operation ofaircraft.

The present invention also relates to a method of management of anairspace comprising a plurality of flyway segments configured to be usedby a plurality of unmanned aircraft comprising the steps ofadministrating the airspace, administrating the aircraft in theairspace, directing the aircraft in the airspace, and monitoringconditions in the airspace. Administrating the airspace comprisesdesignation of a set of zones comprising a set of flyway segments in theairspace for operation of aircraft. Administrating the aircraft alsocomprises registration of aircraft to operate in the airspace.

The present invention further relates to a method of management of anairspace comprising a plurality of flyway segments configured to be usedby a plurality of unmanned aircraft comprising the steps ofadministrating the airspace, administrating aircraft in the airspace,directing aircraft in the airspace, and monitoring conditions in theairspace. Administrating the airspace comprises of designation of a setof zones comprising a set of flyway segments in the airspace foroperation of aircraft. Administrating the aircraft also comprisesregistration of aircraft to operate in the airspace and at least onetransaction with an aircraft.

The present invention further relates to a system for managing anairspace comprising a plurality of flyway segments and at least one zonefor unmanned aircraft comprising a computing system configured (1) foradministrating the airspace and aircraft and (2) for directing aircraftin the airspace, and a monitoring system configured for monitoring ofconditions in the airspace. Administrating the aircraft also comprisesregistration of aircraft to operate in the airspace and at least onetransaction with an aircraft.

The present invention relates to an unmanned aircraft configured foroperation on a mission in an airspace comprising flyway segments managedby a management system of the airspace comprising a profile for theaircraft used for registration of the aircraft with the managementsystem before operation in the airspace, an identifier for the aircraftused for monitoring of the aircraft by the management system duringoperation in the airspace, and a license for the aircraft used by thesystem to manage the operation of the aircraft in the airspace; so thatthe aircraft can be operated according to terms of the license duringthe mission in the airspace. The aircraft can be registered by themanagement system before the mission and monitored by the managementsystem during the mission.

The present invention also relates to an unmanned aircraft configuredfor operation on a mission in an airspace comprising flyway segmentsmanaged by a management system for the airspace comprising a profile forthe aircraft used for registration of the aircraft with the managementsystem before operation in the airspace, an identifier for the aircraftused for monitoring of the aircraft by the management system duringoperation in the airspace, and rights for the aircraft obtained bytransaction and used by the management system to manage the operation ofthe aircraft in the airspace. The aircraft is to be operated accordingto rights obtained to perform the mission in the airspace. The aircraftis registered by the management system before the mission and monitoredby the management system during the mission and charged a rate for useof the airspace determined by terms of the transaction and data obtainedby the management system from data sources.

The present invention further relates to a method of configuring anunmanned aircraft for operation on a mission in an airspace comprisingflyway segments managed by a management system for the airspacecomprising the steps of creating a profile for the aircraft used forregistration of the aircraft with the management system before operationin the airspace, providing an identifier for the aircraft used formonitoring of the aircraft by the management system during operation inthe airspace, and transacting a license for the aircraft used by themanagement system to manage the operation of the aircraft in theairspace. The aircraft is to be operated according to terms of thelicense during the mission in the airspace. The aircraft is registeredby the management system before the mission and monitored by themanagement system during the mission.

The present invention further relates to a method of configuring anunmanned aircraft for operation on a mission in an airspace comprisingflyway segments managed by a management system for the airspacecomprising the steps of creating a profile for the aircraft used forregistration of the aircraft with the management system before operationin the airspace, providing an identifier for the aircraft used formonitoring of the aircraft by the management system during operation inthe airspace, and transacting a transaction for the aircraft to obtainrights for the operation of the aircraft in the airspace; so that theaircraft can be operated according to rights obtained to perform themission in the airspace.

The present invention relates to a method of operating an unmannedaircraft to perform a mission in an airspace comprising zones managed bya management system for the airspace comprising the steps of registeringthe aircraft with the management system, obtaining rights for theaircraft in a transaction with the management system, and performing themission. The aircraft is to be operated according to terms of thetransaction with the management system during the mission in theairspace.

The present invention also relates to a method of operating an unmannedaircraft to perform a mission in an airspace comprising flyway segmentsand at least one zone managed by a management system for the airspacecomprising the steps of registering the aircraft with the managementsystem, transacting a license with the management system providingrights for the aircraft in the airspace at a rate, and performing themission. The aircraft is to be operated according to terms of thelicense during the mission in the airspace.

The present invention further relates to an unmanned aircraft systemconfigured to operate on a mission in an airspace managed by amanagement system for the airspace comprising an aircraft comprising aprofile and an identifier, a license provided to the aircraft by themanagement system at a rate, and a computing system configured toprovide data relating to the operation of the aircraft to the managementsystem. The computing system is connected to data sources to providedata for operation of the aircraft in the airspace.

The present invention further relates to an unmanned aircraft systemconfigured to operate on a mission in an airspace managed by amanagement system for the airspace comprising an aircraft comprising aprofile and an identifier, a license provided to the aircraft by themanagement system, a computing system on the aircraft configured (1) toconduct at least one transaction with the management system and (2) toprovide data relating to the operation of the aircraft to the managementsystem. The computing system is connected to data sources to providedata for operation of the aircraft.

FIGURES AND TABLES

FIG. 1 is a schematic/representational diagram of a UAV/drone craftaccording to an exemplary embodiment.

FIG. 2A is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 2B is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 2C is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3A is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3B is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3C is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3D is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3E is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 3F is a schematic perspective view of an unmanned aircraftaccording to an exemplary embodiment.

FIG. 4A is a schematic plan view of an airspace according to anexemplary embodiment.

FIG. 4B is a schematic plan view of the airspace of FIG. 4A showing aflyway/route for aircraft according to an exemplary embodiment.

FIG. 5A is a schematic plan view of an airspace according to anexemplary embodiment.

FIG. 5B is a schematic plan view of the airspace of FIG. 5A showingflyway/route segments for aircraft according to an exemplary embodiment.

FIG. 6A is a schematic plan view of an airspace according to anexemplary embodiment.

FIG. 6B is a schematic plan view of the airspace of FIG. 6A showingflyway/route segments for aircraft according to an exemplary embodiment.

FIG. 7A is a schematic plan view of an airspace according to anexemplary embodiment.

FIG. 7B is a schematic plan view of the airspace of FIG. 7A showingflyway/route segments for aircraft according to an exemplary embodiment.

FIG. 8A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 8B is a schematic perspective view of the airspace of FIG. 8Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 9A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 9B is a schematic perspective view of the airspace of FIG. 9Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 10A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 10B is a schematic perspective view of the airspace of FIG. 10Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 11A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 11B is a schematic perspective view of the airspace of FIG. 11Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 12A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 12B is a schematic perspective view of the airspace of FIG. 12Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 13A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 13B is a schematic perspective view of the airspace of FIG. 13Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 14A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 14B is a schematic perspective view of the airspace of FIG. 14Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 15A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 15B is a schematic perspective view of the airspace of FIG. 15Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 16A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 16B is a schematic perspective view of the airspace of FIG. 16Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 17A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 17B is a schematic perspective view of the airspace of FIG. 17Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 18A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 18B is a schematic perspective view of the airspace of FIG. 18Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 19A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 19B is a schematic perspective view of the airspace of FIG. 19Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 20A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 20B is a schematic perspective view of the airspace of FIG. 20Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIG. 21A is a schematic perspective view of an airspace according to anexemplary embodiment.

FIG. 21B is a schematic perspective view of the airspace of FIG. 21Ashowing flyway/route segments for aircraft according to an exemplaryembodiment.

FIGS. 22A and 22B are schematic plan diagrams of a multi-zone airspacefor flyways/routes for aircraft according to an exemplary embodiment.

FIG. 23A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 23B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 24A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 24B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 24C is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 25 is a schematic perspective view of segment of airspace accordingto an exemplary embodiment.

FIG. 26 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 27 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 28 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 29 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 30 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 31 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 32 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 33A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 33B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 34A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 34B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 35 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 36 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 37 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 38 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 39 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 40 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 41 is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 42 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 43 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 44 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 45 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 46A is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 46B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 47 is a schematic perspective view of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 48A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 48B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 49A is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 49B is a schematic plan diagram of a flyway segment set in anairspace according to an exemplary embodiment.

FIG. 50 is a schematic block diagram of management and administration ofan airspace system according to an exemplary embodiment.

FIG. 51 is a schematic block diagram of a monitoring system for thesystem according to an exemplary embodiment.

FIG. 52 is a schematic block diagram of a UAV/drone systems in thesystem according to an exemplary embodiment.

FIG. 53 is a schematic block diagram of a network for the systemaccording to an exemplary embodiment.

FIG. 54 is a schematic block diagram of a system/device networking forthe system according to an exemplary embodiment.

FIG. 55 is a schematic block diagram of a network for the systemaccording to an exemplary embodiment.

FIG. 56 is a schematic block diagram of a system/device networking forthe system according to an exemplary embodiment.

FIG. 57 is a schematic block diagram of a the system according to anexemplary embodiment.

FIG. 58 is a schematic block diagram of functions of the systemaccording to an exemplary embodiment.

FIG. 59 is a schematic block diagram of a management system of thesystem according to an exemplary embodiment.

FIG. 60 is a schematic block diagram of a control system of the systemaccording to an exemplary embodiment.

FIG. 61 is a schematic block diagram of a data sets for the systemaccording to an exemplary embodiment.

FIG. 62 is a schematic block diagram of a UAV/drone systems in thesystem according to an exemplary embodiment.

FIG. 63 is a schematic block diagram of a UAV/drone craft in the systemaccording to an exemplary embodiment.

FIG. 64 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 65 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 66 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 67 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 68 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 69 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 70 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 71 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 72 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 73 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 74 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 75 is a schematic process flow diagram showing use/operation of thesystem/airspace according to an exemplary embodiment.

FIG. 76 is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 77 is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 78A is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 78B is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 79 is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 80 is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 81A is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 81B is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

FIG. 81C is a schematic process flow diagram for use/operation of anunmanned aircraft system in the system/airspace according to anexemplary embodiment.

DESCRIPTION

A system and method for management of an airspace for unmanned aircraftis disclosed according to exemplary and alternative embodiments. Anunmanned aircraft configured for operation in a managed airspace is alsodisclosed according to exemplary and alternative embodiments. A systemand method for operation of unmanned aircraft in a managed airspacecomprising flyways for unmanned aircraft traffic is further disclosedaccording to exemplary and alternative embodiments. Each system andmethod comprises a modification/improvement of technology intended tofacilitate management/operation of an airspace for UAV/drone traffic andUAV/drone craft in a safe, efficient manner. According to an exemplaryembodiment, the airspace comprises a set of flyway segments in a set ofzones/regions designated and established with reference to feature theregion under the airspace. See, e.g. FIGS. 4A to 22B. The system andmethod for management of the airspace comprises the administration ofthe airspace, the administration of the UAV/drone craft to operate inthe airspace, the direction of UAV/drone craft in operation in theairspace, monitoring of conditions/aircraft in the airspace, etc. See,e.g. FIGS. 23A to 49B and 50-60. The UAV/drone craft are configured tointeract/transact with the management system with rights/priority and atrates/fees paid for use/access of the airspace and forregistration/operation in the airspace under the monitoring/direction ofthe management system for the airspace. See FIGS. 1-3F and 61-81C.According to an exemplary embodiment, the management system andUAV/drone craft are configured to engage in transactions so that themanagement system functions (among other things) as a commercialenterprise in which UAV/drone craft are registered/managed andoperated/charged for use/access of the airspace according to standardrules/regulations and market-based rates/fees.

System/Management—Introduction

Referring to the FIGURES, the system and method of managing an airspacefor UAV/drone craft is shown schematically according to an exemplaryembodiment. According to an exemplary embodiment, the airspace comprisesa set of flyway segments in a set of zones/regions designated withreference to features such as exist in the region under the airspace.See, e.g. FIGS. 4A to 22B. The system and method for management of theairspace comprises the administration of the airspace, theadministration of the UAV/drone craft, the direction of UAV/drone craftin operation in the airspace, monitoring of conditions/aircraft in theairspace, etc. See, e.g. FIGS. 50-63. According to an exemplaryembodiment, management of the airspace will comprise a set offunctions/tasks of the system and/or a system administrator.

According to an exemplary embodiment, the administration of the airspacewill comprise (among other functions/tasks) designation/establishmentand maintenance of a set/system of flyways and flyway segments withinzones/regions, establishment of protocol/policy and rules/regulationsfor the airspace, compliance with governmental regulation, communicationwith craft/operators of UAV/drone craft, monitoring/evaluation ofconditions in the airspace, etc.

According to an exemplary embodiment, the administration of aircraft(e.g. UAV/drone craft) will comprise (among other functions/tasks)registration of aircraft (e.g. collection and/or verification ofinformation relating to the craft), transactions with aircraft,assignment of rights/privileges and priority/status to aircraft,registration of missions for aircraft, creation of a profile (e.g. datafile/set of information) for craft operating in the airspace, assignmentof routes for craft operating in the airspace, monitoring/enforcement ofrules/regulation for aircraft operating in the airspace, etc.

According to an exemplary embodiment, an aircraft that is to conduct amission (e.g. travel into and/or through the airspace of theadministrator) will register the mission with the administrator of thesystem. According to an exemplary embodiment, registration of themission will include collection and/or verification of data/informationrelating to the mission date; destination, departure, time of day,route, speed, etc.

According to an exemplary embodiment, direction of aircraft willcomprise communication with and/or direction/control of control of craftin operation during a mission and related management of traffic andother functions.

According to an exemplary embodiment, monitoring of conditions in theairspace and of aircraft will comprise the functions of monitoringenvironmental conditions and traffic and other conditions.

According to an exemplary embodiment, the system and method isconfigured to manage and administrate the airspace as a commercialoperation in which transactions with the system UAV/drone craft purchaserights/licenses and/or pay fees/tolls at commercial rates forpassage/access and use of the airspace. As indicated schematically, useand access of the airspace may be provided at rates that vary accordingto factors (including the size/type of craft, time/day of travel, flywayzone/lanes in use, conditions in the airspace/traffic,environmental/weather conditions, commercial considerations, etc.).License rights/rates for UAV/drone craft may be determined before amission of the craft in the airspace, during the mission, and after themission (i.e. the system and craft may be configured for “dynamic”transactions that occur when the craft is in operation in the airspace).

According to an exemplary embodiment, license rights for use/access ofthe airspace may be sold by a single vendor, at multiple outlets, inmultiple markets (e.g. primary and secondary, etc.). Commercialentities/other entities or vendors operating the system may obtainrights/easements from and through governmental/municipal agencies and/oroperate in conjunction with such agencies to establish/designate andoperate flyways in an airspace in a region. According to an exemplaryembodiment, rates for license/rights for use/access of the airspace canbe adjusted by market pricing/effects and sold/traded by brokers who mayemploy various business strategies.

According to an exemplary embodiment, the system may facilitate theoperation of any present or future type/configuration of UAV/drone craftin the airspace. Such UAV/drone craft may be operated by an operator(e.g. pilot/system) at a remote station (see e.g. FIGS. 52 and 53) or byother methods/systems. According to an exemplary embodiment, theUAV/drone system (e.g. craft with control/communication system) will beconfigured to transact (e.g. register and/or license) with the systemand to communicate (e.g. tracking/monitoring and/or data transmission bynetwork connection, etc.) to facilitate the operation of the UAV/dronecraft in the airspace and the management of the airspace by the system(e.g. according to protocol/policy, rules/guidelines, legal/regulatorycompliance, etc.).

According to an exemplary embodiment, the system will function as partof a commercial enterprise using data from data sources (includingUAV/drone craft) to establish safe and efficient methods of managementfor the airspace in a commercially successful manner (e.g. withappropriate rates set and billed/paid by or on behalf of UAV/drone craftin operation in the airspace). According to an exemplary embodiment,UAV/drone craft in operation and the system for the airspace will beadapted for interaction as indicated, for example, in the FIGURES.

Configuration of UAV/Drone Craft

Referring to FIGS. 1, 2A-2C and 3A-3F, unmanned aerial/air vehicles(UAV) or drone aircraft (UAV/drone craft) are shown schematicallyaccording to exemplary/representative embodiments. As indicatedschematically, a UAV/drone craft may be provided in any of a variety offorms, shapes, sizes, capabilities, etc. according to exemplaryembodiments, including a fixed wing configuration (such as commonlyreferred to as an airplane) (see FIGS. 2A-2C) or rotating bladeconfiguration (such as commonly referred to as a helicopter) (see FIGS.3A-3F) or any other form that presently exists or may exist astechnology for UAV/drone craft evolves in the future. According to anyexemplary embodiment, the management system and airspace can beconfigured to operate with any of a wide variety of types and forms ofUAV/drone craft. As indicated, FIG. 1 is intended to show aschematic/representational form of a UAV/drone craft of any form able tooperate in the airspace managed by the system and method according toexemplary and alternative embodiments. See also FIGS. 22A to 49A/B.

According to an exemplary embodiment, the system is configured tomanage/direct any UAV/drone craft capable of operation in flywaysegments and zones/regions of the airspace under the control of anoperator/pilot or with a suitable control system that can be directed tooperate the UAV/drone craft in and along an assigned route in theairspace. According to an exemplary embodiment, the UAV/drone craft maycomprise an on-board computing system with a control module that can beaccessed by a remote operator and/or by network to direct the UAV/crafton a route/mission and to track location, speed, etc. See e.g. FIGS.50-56 and 61-63.

According to an exemplary embodiment, the system comprises a monitoringsystem (e.g. detectors and data links/communications) to monitorUAV/drone craft operating in the airspace (e.g. includingposition/location, speed, time, time of day, etc.) so that the systemcan determine rates to be charged. According to an exemplary embodiment,the detectors may comprise transceiver/transponder technology such asused in toll roads with the EZ-PASS system. See e.g. U.S. Pat. No.5,819,234 and U.S. Patent Application Publication No. 2011/0161140 (e.g.using RFID/DSRC or other technology). According to an exemplaryembodiment as indicated schematically in FIG. 3F and FIG. 16B, aUAV/drone craft may comprise a detector-ready device (e.g.transceiver/transponder) configured to connect by data communicationswith a detector of the system (e.g. to manage a checkpoint or otherwisetrack the UAV/drone craft across flyway segments and zones/regions).According to other exemplary embodiments, the UAV/drone craft maycomprise a wireless communication device (e.g. employing conventionalwireless/radio/cellular/other technology) configured to be detected bythe monitoring system (e.g. at detectors of the system) along the flywaysegments during a mission. According to an exemplary embodiment, theUAV/drone craft will comprise an identifier (such as a uniquealphanumeric code of a type appearing on a visible license plate for aregistered motor vehicle, a unique RF code, or the like). See FIG. 3F(e.g. UAV/drone craft with schematic representation of identifier I as adevice/system/object to function passively and/or actively to allowidentification of UAV/drone craft to the system including duringoperation in the airspace).

According to an exemplary embodiment, a UAV/drone craft may comprise adata collection system including for example a global positioning system(GPS) (or other technology) that will record/track the position/path ofthe UAV/drone craft and create data/data file(s) that can be transmittedto the system during the mission (e.g. continuously, at intervals,periodically/when possible/when data connector can be established, whenqueried, etc.) or after the mission (e.g. at a detector in the airspace,at an exit station from the airspace, by direct data link, by networkconnection, from the operator/by the pilot, etc.); as indicated, theUAV/drone craft may operate at the direction of a remote pilot/operatorand data may be transmitted to the system by the pilot/operator networkconnection. According to an exemplary embodiment, a UAV/drone craft maycomprise an imaging system such as a camera that records images that aretransmitted to the system (e.g. time/date-stamped photographs takenduring operation on the route and/or at checkpoints and markings, etc.)to record the position/path (and other information such as speed, etc.)for the UAV/drone craft to transmit to the system (e.g. in or nearreal-time during the mission or after completion of the mission). Asindicated schematically in FIG. 3F an identifier I (e.g. device tofacilitate/transmit identification) is provided on the UAV/drone craft;the identifier is intended to represent any device/system that can bemounted/installed or placed on a UAV/drone craft (e.g. detector, GPS,transceiver/transponder, camera, identifier, etc.).

According to an exemplary embodiment, the UAV/drone craft will comprisea device/system for data recording, a data communication system, acomputing/control system, as well as other systems for operability ofthe UAV/drone craft in flight.

According to an exemplary embodiment, the UAV/drone craft will beprovided a profile (e.g. data set/file) comprising the attributes of theUAV/drone craft to facilitate administrator and director (e.g.transacting, registering, tracking/monitoring, communications, control,licensing, billing, payment, etc.) of the UAV/drone craft and managementof the airspace. See FIGS. 61-63. According to an exemplary embodiment,the registration/profile of a UAV/drone craft will indicate to thesystem the method and manner of anticipated operation and interaction ofthe UAV/drone craft in the airspace. (According to an exemplaryembodiment, UAV/drone craft having enhanced data/communication andcontrol/direction capability may be entitled to enhanced status,discounted rates, etc. in the airspace.) According to an exemplaryembodiment, UAV/drone craft will operate in the airspace to perform amission according to assigned rights/priority/status and routing by thesystem subject to tracking/monitoring and will be billed/obligated topay for use/access of the airspace at a rate/terms transacted with thesystem (e.g. by license). According to an exemplary embodiment, therate/terms and rights/priority/status will be contained in the profileof the UAV/drone craft as a data set (along with billing/payment andoperation history). See e.g. FIGS. 61-63.

Designation of Airspace/Flyways

As indicated in the FIGURES; according to an exemplary embodiment, anairspace may exist or be established in any of a wide variety ofenvironments in any of a wide variety of terrain/layout with any of awide variety of features that may experience any of a wide variety ofconditions. As indicated schematically in FIGS. 4A to 22B, according toan exemplary embodiment the flyways/routes and zones/regions in anairspace can be designated and configured based on theenvironment/terrain, features and conditions that exist or that may beexperienced by UAV/drone traffic and craft (or other purposes). Asindicated in the FIGURES, features may include geologic features,geographic features, man-made features, natural features and otherfeatures, for example, hills/mountains, valleys, plains/open spaces,rivers/creeks, canals, lakes, ponds, roads/streets,highways/expressways, rail/transit lines, walkways/sidewalks,trails/paths, buildings/structures, commercial/office complexes,business/industrial locations, urban centers, homes/apartments, shoppingcenters/malls, water towers, utility installations, power/communicationtowers, power/communication transmission lines, pipelines, fences,basements, borders, excavations, trees/forests, fields/farms,transportation ports/stations, easements, obstacles, etc. According toan exemplary embodiment, such features may be used to designate anddevelop and establish routes and flyways in an airspace; such flywaysand zones may be configured for or based upon the features, terrain andenvironment/conditions that exist.

According to an exemplary embodiment, the airspace will comprise a setof flyways/zones providing routes for craft operating in the airspacesuitable for the airspace and craft in view of the environment,features, conditions, terrain, etc.

According to an exemplary embodiment, as indicated in FIGS. 4A through22B, flyways/zones may be designated with reference to features on theunderlying terrain such as roads, streets, highways, expressways,waterways, rivers, canals, railways, utility lines, easements, powertransmission lines, pipelines, other geographic features, etc.

As indicated, flyways/zones may be established to comprise a transitnetwork to facilitate safe and convenient/efficient operation andpassage of craft in the airspace. According to an exemplary embodiment,flyways/zones may be configured in a manner to designate/segregate craftaccording to type and/or priority and/or mission and/or route. Asindicated schematically, for example, a flyway segment designated withreference to a street may be used for “local” craft operating atrelatively lower speed and performing localized missions while a flywaysegment designated with reference to a rail/transit line or river orexpressway may be used for “express” craft in passage through theairspace and/or operating at relatively higher speed; for example, azone designated over an urban area may be used for “local” craft oroperation in the urban area while a zone designated over anon-urban/outlying area may be used for “express” craft in passagethrough the airspace. See FIGS. 4A through 22B.

As indicated, routes for UAV/drone craft on a mission in the airspacecan be assigned to comprise flyway segments and zones appropriate forsafe and efficient operation of the craft and traffic management.According to other exemplary embodiments, flyway segments can beoccupied by the UAV/drone craft while carrying out aspects of a mission,either directly (e.g. for imaging/sensing while traveling along a flywaysegment, for picking up or dropping off a parcel at a locationunderneath a flyway segment, etc.) or indirectly (e.g. for travel to orfrom a site at which mission operations are performed). In someembodiments, zones can be occupied by the UAV/drone craft while carryingout aspects of a mission (e.g. a UAV/drone craft may acquire rights toperform imaging/sensing or parcel pickup/delivery at any location withina zone, to hover/loiter/travel freely within the zone, etc.). See FIGS.23A to 49B.

Referring to FIGS. 4A through 22B, various representative diagrams ofairspaces for UAVs/drone craft of various types are shown schematicallyaccording to an exemplary embodiment. As indicated, the airspaces can belocated in any of a wide variety of geographic locals and regions(including those of a type shown in the FIGURES and other locations); asindicated such locales and regions may comprise zones having varioustypes/forms and density of features (such as ports, roads, rail lines,rivers/waterways, buildings, sites, trees, towers, etc.) as well as ofterrain (such as hills, valleys, etc.). As indicated, designatedflyways/routes for UAV/drone craft can be provided or established ineach zone or region of an airspace. (In FIGS. 4A/4B through 21A/21B, inthe “A” figure the airspace is shown with terrain/featuresschematically/representationally; in the “B” figure with examples of theairspace of the “A” figure is shown flyways/routes for UAV/drone trafficin the airspace.)

According to an exemplary embodiment (as indicated schematically), in anairspace providing a network of features such as roads/streets,highways/expressways, rivers/waterways, rail/transit lines, etc., acorresponding network of flyways/routes for UAV/drone craft can beprovided. Passage of UAV/drone craft in an airspace can be administeredand managed on designated flyways/routes and zones/regions in theairspace (e.g. with reference to the corresponding features on whicheach flyway is designated). According to an exemplary embodiment,establishment of designated flyways/routes for UAV/drone traffic in anairspace will facilitate safe and efficient managed passage and transitof UAV/drone craft in and through the airspace. As indicated, accordingto an exemplary embodiment, flyways/routes can be designated by featuresunder the airspace or by other considerations notwithstanding featuresunder the airspace so as to facilitate safe/efficient management andadministration of UAV/drone craft in the airspace.

According to an exemplary embodiment, the airspace will be configured toprovide ports and stations to provide utilities for craft (e.g.refueling/recharging, service/maintenance, parking, shelter, etc.). SeeFIGS. 5A, 9A, 21A, 35-36. According to an exemplary embodiment, theairspace may be configured to assist/retrieve disabled or downed craftby facilitating access by service crews.

Referring to FIGS. 4A and 4B, an airspace over terrain with featuressuch as a river V, creek K, roads R, highway H, municipal/commercialairport A and UAV/drone airport P is shown schematically andrepresentationally. The airspace (and features) with designatedrepresentative flyways/routes F for UAV/drone traffic is shownschematically and representationally in FIG. 4B. As indicated in FIG.4B, flyways/routes for UAV/drone traffic can be designated withreference to features and terrain in the airspace of FIG. 4A. Forexample, as indicated in FIG. 4B, routes/flyways F for UAV/drone trafficconnecting UAV/drone airport/station T and elsewhere in the airspace aredesignated over creek K, road R, highway H, river V. (A conventionalairport A for conventional aircraft is shown.)

Referring to FIGS. 5A and 5B and FIGS. 6A and 6B, an airspace over anurban area/zone is shown schematically; flyways F for UAV/drone trafficin the airspace of FIGS. 5A and 6A are designated over rail line L,roads/streets R, river V, highway H as shown schematically andrepresentationally in FIGS. 5B and 6B. Station T is shown connected tothe network of flyways in FIGS. 5A-5B.

Referring to FIGS. 7A and 7B, an airspace over an urban/commercial zoneor region is shown schematically and representationally. As indicatedschematically in FIG. 7B, flyways F for UAV/drone traffic are designatedover features such as rail/transmit line L, expressway/highway H,streets/roads R, river V, etc.; as indicated schematically, interchangesfor craft can be provided generally in a manner as used forinterchange/routing of ground vehicle traffic. According to otherembodiments, flyways can cross over each other at different altitudes.See also FIGS. 33A/B and 34A/B. As also indicated schematically in FIG.7B, routes to locations such as residential homes, commercial businessoffices, factories/industrial plants, schools, hospitals, etc., can bedesignated or established for UAV/drone craft (e.g. as a delivery routeto a representative building).

Referring to FIGS. 8A and 8B, an airspace in a rural/farm area/zone orregion is shown schematically with features in the farmland such asrail/transit line L, streets/road R, highway H; flyways F for UAV/dronetraffic can be designated over the features in the airspace as indicatedschematically and representationally in FIG. 8B; delivery route FD shownas following a flyway and exiting to a farm/rural residence is alsoshown schematically.

Referring to FIGS. 9A and 9B, an airspace in anurban/industrial/commercial zone or region is shown schematically withfeatures such as office buildings, factories, warehouses, distributionlocations, residential buildings, schools/educational centers, municipalbuildings/offices, etc. and streets, roads/drives, highways, transitlines, etc. Flyways F for UAV/drone traffic and routes for delivery canbe designated in the airspace as indicated schematically andrepresentationally in FIG. 9B. Stations T for craft are shownschematically in the zone and flyway network.

Referring to FIGS. 10A and 10B, an airspace in a suburban/residentialzone/community or region is shown schematically and representationallywith features such as residential homes, multi-family housing buildings,other structures, streets/roads, lots, driveways and trees. Designatedflyways are indicated including routes for delivery shown schematicallyand representationally over streets and driveways in FIG. 10B. ObstaclesO shown as trees are shown schematically in the zone and adjacent theflyway network.

Referring to FIGS. 11A and 11B, an airspace in a rural zone/terrain orregion is shown schematically and representationally with features suchas a river, mountainous terrain, hills/valleys, rail/transit lines,roads, highway/expressway, river/waterway, etc. Designated flyways F forUAV/drone traffic are indicated schematically and representationallyover rail/transit line, road, expressway and river/waterway in FIG. 11B.As further indicated, flyway segments in the zone/airspace may havedifferent lengths/configurations/shapes and distances depending upon thecorresponding reference features in the airspace used to designate theflyway segment. As indicated, the flyway segment over theexpressway/highway and the flyway segment over the rail line have agenerally more linear and direct configuration/shape; the flyway segmentover the river has a multi-curve and meandering configuration/shape.(All flyway segments avoid obstacles such as mountainous terrain in thezone.)

Referring to FIGS. 12A and 12B, an airspace in a rural zone/terrain orregion is shown schematically and representationally with features suchas a mountain/valley, road, trees, hills and a utility line/power cutover the mountain. Designated flyways F for UAV/drone traffic are shownschematically and representationally over the road and over the utilitycut in FIG. 12B; UAV/drone traffic is also indicated schematically andrepresentationally in FIG. 12B. As indicated in FIG. 12B flyway segmentsin the zone/airspace may have different lengths or distances dependingupon the corresponding reference feature; UAV traffic has a more directroute of shorter distance on the flyway designated over the utility cut;UAV traffic has a less direct route of longer distance on the flywaydesignated over the road.

Referring to FIGS. 13A and 13B, an airspace in a rural zone or region isshown schematically and representationally with features such as agenerally flat terrain with a highway and obstacles O shown as windpower turbines and cellular/radio communications towers. Designatedflyway F for UAV/drone traffic is shown schematically over the highwaybetween the wind power turbines and cellular communication towers inFIG. 13B. As indicated schematically in FIGS. 13A and 13B, detectors Dfor a monitoring system for the airspace may be installed on structuressuch as towers in the airspace.

Referring to FIGS. 14A and 14B, an airspace in a rural/mountainousterrain or region is shown schematically and representationally withfeatures such as a river, mountains, and an expressway/highway.Designated flyways F for UAV/drone traffic are shown schematically overthe river and over each lane of the expressway (between the obstructionof mountains) in FIG. 14B. As indicated, flyway segments in thezone/airspace may be designated different routing to permit differentUAV/drone traffic of different priorities, at different speeds, ofdifferent types, etc. See also FIGS. 11A and 11B.

Referring to FIGS. 15A and 15B, an airspace in a rural/mountain zone orregion is shown schematically and representationally with features suchas a mountain/valley, road, trees/plants, hills, etc. Designated flywayF for UAV/drone traffic is shown schematically over the road winding(with the road) around a cut for the highway (in avoidance of obstaclesO) in FIG. 15B. See also FIGS. 12A and 12B.

Referring to FIGS. 16A and 16B, an airspace in an urban/suburban zone orregion is shown schematically and representationally with features suchas a boulevard/street with multiple lanes, buildings, sidewalks, medianstrips (between lanes on the street/boulevard), a water tower, hills,trees, etc. Designated flyways F for UAV/drone traffic are shownschematically over each lane of the boulevard/street in FIG. 16B (e.g.in avoidance of obstacles O shown as tower and trees). As indicatedschematically, each lane of flyway may be designated for unidirectionaltravel of UAV/drone traffic (e.g. with reference to the direction oftravel of vehicles on the corresponding lane on the street/boulevard).UAV/drone traffic in a flyway lane may be routed with or counter tovehicle traffic in the corresponding street lane (below the flywaylane). Also indicated schematically in FIGS. 16A and 16B is a set ofdetectors D (e.g. sensor, transponder, camera, antenna, node, wirelessaccess point, etc.) for UAV/drone craft atop buildings along the flyway;as indicated UAV/drone traffic in the flyway/zone may betracked/monitored and/or in data communication with the system duringoperation in the airspace through the monitoring system and data/networkconnections. As shown schematically, according to an exemplaryembodiment the detector/antenna/etc. of the monitoring system can beconfigured to obtain data/information from the craft (e.g. such asidentifier I shown schematically on craft UAV in FIG. 3F) in a one-wayand/or two-way data transmission (e.g. RFID track, data link, networklink, imaging, etc.).

Referring to FIGS. 17A and 17B, an airspace in a rural/outlying zone orregion is shown schematically and representationally with features suchas farm fields, a rail/transit line, a rail/road crossing with signal, aroad/highway, etc. Designated flyways F for UAV/drone traffic are shownschematically over the rail/transit line and over the road/highway inFIG. 17B; as indicated in FIG. 17B the flyway over the rail/transit lineis positioned above the flyway designated over the road/highway. As alsoindicated schematically, a detector D (e.g. sensor, transponder, cameraetc.) is provided at the rail crossing so as to be able to detectUAV/drone traffic in each flyway. UAV/drone traffic is also indicatedschematically in each of the flyway segments shown in FIG. 17B.

Referring to FIGS. 18A and 18B, an airspace in a suburban/rural/outlyingzone or region is shown schematically and representationally withfeatures such as an expressway (with bidirectional lanes for roadtraffic), an overpass for a crossing road/highway, etc. Designatedflyways F for UAV/drone traffic are shown schematically over theexpressway and over the road/overpass in FIG. 18B. As indicatedschematically, a detector D (e.g. sensor, transponder, imaging camera,etc.) is provided at the overpass so as to be positioned to detectUAV/drone traffic in each of the flyways.

Referring to FIGS. 19A and 19B, an airspace in a rural/suburban zone orregion is shown schematically and representationally with features suchas a road, utility lines, access road, trees and other terrain, etc.Designated flyways F for UAV/drone traffic are shown schematically overthe road and over the utility lines/wires or posts/poles in FIG. 19B. Asindicated schematically, each of the flyways may be arranged with lanesfor bidirectional UAV/drone traffic in a different manner orarrangement; the flyway over the road shows a bidirectional set of twolanes oriented in a horizontally parallel (side-by-side) arrangement;the flyway over the utility lines/wires shows a bidirectional set of twolanes oriented in a vertically parallel (stacked) arrangement.

Referring to FIGS. 20A and 20B, an airspace in a rural/suburban zone orregion is shown schematically and representationally with features suchas a highway with exit ramp, hills/terrain, trees, and an approachingweather condition shown as a rainstorm (indicated as obstacle O) amongother features. Designated flyway F for UAV/drone traffic is providedover the highway with an exit flyway provided over the exit ramp in FIG.20B. As indicated schematically in FIG. 20B, with the approach of athreatening weather condition (such as a rainstorm) UAV/drone traffic(shown schematically by a UAV/drone craft as indicated) is able to exitfrom the main flyway and threatening condition and proceed to analternative route or shelter in an effort to avoid the condition(indicated as obstacle O). Referring to FIGS. 21A and 21B, therural/suburban zone or region is shown to provide a structure/buildingproviding a station/shelter T for UAV/drone craft. As indicatedschematically in FIG. 21B, one UAV/drone craft has entered the shelteras another UAV/drone craft is approaching the shelter to land to avoidthe approaching weather condition (e.g. rainstorm). As indicatedschematically, utilities and services may be provided to UAV/drone craftat the station/shelter, for example, at a refueling/recharging system P.

According to any preferred embodiment, the flyway and flywaysegments/lanes for UAV/drone traffic will be designated in a place thatfacilitates safe and efficient travel of UAV/drone craft, includingelevation/distance and separation from features, vehicles, obstacles,etc. at or near/adjacent to the flyway segment/lane.

Flyway/Route/Segments/Zones

As indicated schematically in FIGS. 4B to 21A/B and shown schematicallyin FIG. 22A/B, according to an exemplary embodiment, flyways/routes inand to or through an airspace can be configured or arranged intozones/regions. According to an exemplary embodiment, flyway/flywaysegments and zones/regions can be designated in the airspace andconfigured for use for routes/routing with reference to features in theregion under the airspace; in the designation of flyways/routes,zones/regions may be differentiated based upon various considerations;such conditions may include features in the zone, conditions in thezone, traffic in the zone, events occurring in the zone, occupancy inthe zone, etc. As indicated generally in FIGS. 4A to 21A/B and 22A/B,routes for a UAV/drone craft using flyways/flyway segments in anairspace may comprise multiple route segments using multiple flywaysegments that may enter and exit multiple zones.

According to an exemplary embodiment, a mission for a UAV/drone craftmay comprise route comprising a series of segments that may havedifferent designations. For example, a UAV/drone craft on a mission todeliver a parcel to an industrial facility may take a route having asegment designated over a rail/transit line to the municipality and thenhaving a segment over an expressway and then a segment over a highwayand then a segment over municipal streets including to the streetaddress/delivery location at the industrial facility. See e.g. FIG. 9B.

UAV/drone traffic within airspace may be managed and administrated byallocating zones to each UAV/drone craft in routing a UAV/drone trafficin and through flyways in the airspace. Allocating zones for passage inthe routing of each UAV/drone craft may comprise routing differentUAV/drone craft on different/separate flyway segments or routingdifferent UAV/drone craft on different lanes with a flyway segment. Forexample, as indicated schematically in FIG. 22A/B, different flywaysegments (e.g. with different routing over different features) may eachcomprise a separate zone with separate rights and restrictions (e.g.elevation, speed limit, access/entry/exit restrictions, etc.); asindicated schematically in FIGS. 23A through 49B (in variousembodiments) different unidirectional lanes of a flyway segment may(with similar/identical routing over similar/identical features) eachcomprise a separate zone with separate rights and restrictions (e.g.speed limits, access restrictions, etc.).

Rates for travel by a UAV/drone craft may vary dependent upon the zonesof travel and the time of the UAV/drone craft in each zone, as well asother considerations (e.g. as a product of multiple factors). Seegenerally FIGS. 4A-8B, 9A to 21B and 22A/B.

Referring to FIG. 22A/B, an airspace divided into zones is shownschematically and representationally; the airspace comprises zone A,zone B, zone C and zone D. As indicated schematically, zone A may berepresentative of a dense urban area (see e.g. FIGS. 6B, 7B, 9B and16B); zone B may be representative of a less dense transitional orresidential area (see e.g. FIGS. 7B and 10B); zone C may berepresentative of a less dense/bypass transitional area (see e.g. FIGS.4B, 18B and 19B); zone D may be representative of an outlying or ruralarea (see e.g. FIGS. 8B, 13B, 14B and 15B). UAV/drone craft W travelsonly in zone D; UAV/drone craft X travels in zone C and zone D in a moredirect passage; UAV/drone craft Y travels in zone B and zone C and zoneD in a more direct passage; UAV/drone craft Z travels in zone A and zoneB and zone C and zone D in a direct route.

As indicated in the administration of use/access of the airspace (e.g.rate-setting, licensing, billing, etc.), rates for passage of aUAV/drone craft through a zone may be differentiated based on a varietyof factors such as zone density, zone traffic, etc., as well as based onthe type of craft, time of day, etc. For example, the rate for passagethrough zone A may be greater than the rate for passage through zone Bwhich may be greater than the rate for passage through zone C; zone Dmay have the lowest rate for passage. UAV/drone craft traveling throughan airspace comprising multiple zones with differentiated rates forpassage may make route determinations that include consideration of therates for passage (as well as other need/requirements and preferencerelating to the mission or duty of the craft). For example, UAV/dronecraft W may have determined to pass through the airspace in a lessdirect but lower cost route; UAV/drone craft Z may have determined topass through the airspace in the most direct and higher cost route.UAV/drone craft X and UAV/drone craft Y may have balanced considerationsof time/distance and cost in a route determination.

According to an exemplary embodiment, flyway lanes and zones within aflyway in an airspace may be designated not only with reference tofeatures but also with reference to elevation or arrangement (e.g.horizontal or vertical or separation/spacing) or time.

According to an exemplary embodiment, flyways and zones may bedesignated at particular elevations with reference to features in theairspace. As indicated schematically, for example, in FIGS. 19B and26-27, 29-30 and 33A/B-34A/B (among other FIGURES), a flyway maycomprise multiple lanes for UAV/drone traffic; in a flyway, lanes forbidirectional travel of UAV/drone craft may be orientated in ahorizontal arrangement (see FIGS. 19B and 27) or in a verticalarrangement (compare FIGS. 33A/B and 34A/B). Within a region of theairspace, different flyway segments may be considered to be differentzones for purposes of administrating rates/priority, access/speed, etc.(e.g. at various times of day or days of the week, peak periods ornon-peak periods). For example, in FIG. 19B two parallel flyway segmentsare shown; in a peak period, the flyway segment above street R may betreated as a priority zone (e.g. with higher speed/rate and restrictedaccess) and the flyway segment above utility lines U may be treated as astandard/regular zone (e.g. at standard rate and access). According toan exemplary embodiment, flyway lanes and zones within a flyway in anairspace may be designated not only with reference to features but alsowith reference to elevation or arrangement (e.g. horizontal or verticalor separation/spacing) or time.

Registration/Licensing of Craft

According to an exemplary embodiment, the system is configured totransact with UAV/drone craft to register and license UAV/drone craftthat will operate in the airspace.

According to an exemplary embodiment, registration of UAV/drone craftwill include collection and/or verification of information from andabout the UAV/drone craft and operator of the UAV/drone craft (e.g.creation or registration of a profile).

According to an exemplary embodiment, licensing of craft will include atransaction with the craft and operator of the craft to assign andapprove rights and privileges of the craft in operation in the airspace.Rights and privileges of a craft may include items as indicated, such aspriority, status, access, restrictions, etc. According to an exemplaryembodiment, different individual craft in the airspace may be operatingwith different individual rights and privileges (e.g. that may have beenacquired by different types of transactions and at different times andin different manners).

For example, in the airspace a first craft may register and be licensedto operate at a high-level priority status, a second craft may registerand be licensed to operate at a mid-level priority status; a third craftmay register and be licensed to operate at a low-level priority status.The craft operating at high-level status may be given priority overcraft operating at low-level status or mid-level status, including theright to operate in preferred flyways (e.g. to use the fastest or mostdirect route), the right to travel at a higher speed, the right to entercongested flyways (e.g. to displace or ground lower-priority craft inthe flyway), etc.; all craft in the airspace will be obligated to complywith protocol policy and rules/regulations for operation in the airspace(subject to fines, sanctions, restriction, exclusion, etc. fornon-compliance).

According to an exemplary embodiment, registration of the craft is atransaction with the system; upon registration the craft is providedwith a profile (or updated profile if the craft had an existing profile)to allow communications and billing/payment for operation in theairspace. According to an exemplary embodiment, licensing of a craft(e.g. granting by system of a license) is a transaction that can beconducted with the system before a mission (e.g. at time of registrationof a mission).

According to an exemplary embodiment, UAV/drone craft may be configuredto participate in a market for use/access of the airspace and/or toparticular flyway segments and zones/regions in the airspace at aparticular level of access/priority. UAV/drone craft may operate atstandard rates for standard access/priority and routing. According to anexemplary embodiment, transit by a UAV/drone craft in a particularzone/region/flyway of the airspace at a particular time of day/day ofweek or under certain conditions (e.g. during a special event) mayrequire enhanced (non-standard) access; a transaction and/or acquisitionby the UAV/drone craft of enhanced or upgraded rights/privilege (e.g. ata higher rate/fee may be required to upgrade/enhance access); after thetransaction, the UAV/drone craft will have a priority for transit in thezone/region. Other UAV/drone craft that may be potential obstructionsmay be directed by the system to leave the zone/region and re-route (orland) to yield priority to a UAV/drone craft that has obtained higherpriority on a route. A UAV/drone craft identified as a potentialobstruction may instead transact (e.g. bid, offer, purchase) to acquireenhanced rights/privileges in the market to remain in transit in thezone/region.

As indicated, according to an exemplary embodiment, the system andUAV/drone craft may be configured to conduct “dynamic” transactions(e.g. transactions made with the system during operation in theairspace); a dynamic market may exist (e.g. including third-partyvendors) where dynamic transactions can be conducted for UAV/dronecraft. Dynamic transactions may comprise licenses and/or re-routing,etc.

Rates/Fees for Registration/Licensing

According to an exemplary embodiment, UAV/drone craft operating in theairspace may be assessed a base/standard registration fee and then anadditional license fee (at a rate based on terms such as status e.g.rights/priority and privileges). According to an exemplary embodiment, aUAV/drone craft may adjust the status in the airspace by adjusting thelicense/terms. According to an exemplary embodiment, the rates forlicense fees for a UAV/drone craft may be set according to prioritystatus, rights and privileges (e.g. speed limit, separation/spacing,occupancy, size, shape, restrictions, flyway access) and subject toconditions in the airspace (e.g. weather, traffic, etc.) the attributesof the UAV/drone craft, time of day/day of week, other factors, etc. Forexample, if a UAV/drone craft requires or desires to have higherpriority status in the airspace, (e.g. for a particular mission) thelicense may be adjusted so that the UAV/drone craft obtains higherpriority status. According to an exemplary embodiment, rates for licensefees in the airspace may be higher for higher priority status and/orgreater rights and privileges.

According to an exemplary embodiment, rates/fees for use/access of theairspace may be based (in part) on the configuration of flyways andzones/regions in the airspace. Zones/regions in the airspace may bedesignated with reference to an area (e.g. two dimensional), withreference to a volume/space (e.g. three dimensional), and with referenceto time (e.g. four dimensional). For example, according to an exemplaryembodiment, a zone/region may change in shape as a function of time; asindicated schematically in FIG. 22A/B, four zones may be designated inoperation for a high-traffic/peak time of a weekday (e.g. zones A, B, C,D each function at separate rates/access costs); two zones may bedesignated in operation in a low-traffic/off-peak time of a weekday oron a weekend (e.g. zones A/B function as a single zone at one rate andzones C/D function as a single zone at one rate).

According to an exemplary embodiment, rates/fees for use/access of theairspace may be based (in part) on the occupancy of the flyway andzones/regions in the airspace (e.g. rates increase in periods of highoccupancy/traffic). According to other exemplary embodiments, aUAV/drone craft can (for a sufficiently high rate) acquire exclusiverights to occupy a designated zone or flyway segment during a specifiedtime period. In some embodiments, the exclusive rights may be limited tospecified activities, e.g., while other UAV/drone crafts may be allowedto occupy the zone or flyway segment, only a given UAV/drone craft ispermitted to take photographs within it, or the given UAV/drone craft isthe only one permitted to deliver/pickup parcels, etc.

According to an exemplary embodiment, rates/fees for use/access of theairspace may be based (in part) on the type of UAV/drone craft and/orthe manner of control/operation and/or the manner of data communicationsand/or other factors. For example, UAV/drone craft that can or wish tooperate at a high speed may be charged a different rate/fee (e.g. higherrate for use of a higher speed flyway segment or lane); UAV/drone craftthat are under real-time control may be charged a different rate tooperate in the airspace (e.g. a discounted rate may be available forUAV/drone craft that are able to respond to directives and alerts fromthe system during operation in the airspace, for example, to relinquisha lane place/occupancy or move to another lane or re-route, etc.) (seee.g. FIGS. 33A/B-34A/B and 48A/B-49A/B); UAV/drone craft that are inreal-time data communication and/or that will provide post-mission datamay be charged a different rate (e.g. a discounted rate may be availablefor craft that provide status/condition/location data to the system atregular/specified intervals during transit in the airspace or that carrya transponder/tag or other detection device or system that facilitiesmonitoring by detectors in the system along the flyway or that transmitdata such as GPS tracks/coordinates during transit in the airspaceand/or at the conclusion of the mission).

According to an exemplary embodiment, the total rate charged to theUAV/drone craft is a product of the rate for each flyway segment/zoneused by the UAV/drone craft and the time the UAV/drone craft was in theflyway segment/zone. Referring to FIG. 22 according to an exemplaryembodiment, UAV/drone craft W would be charged a total rate comprisingthe standard (base) rate for its time in zone D plus the incrementallyhigher rate for its time in zone C plus the next incrementally higherrate for its time in zone B plus the premium rate for its time in zoneA; UAV/drone craft Z would be charged a total rate comprising thestandard (base) rate for its total time (all) in zone D. (As indicatedschematically in FIG. 22, UAV/drone craft Z had a longer (e.g. slower)route taking more time than UAV/drone craft W on a shorter (e.g. faster)route through the airspace; operators are able to use rate/timeprojections to estimate/budget for total cost and/or total time whenplanning a mission in the airspace.) According to an exemplaryembodiment, UAV/drone craft may plan a mission in the airspace inconsideration of cost/budget factors and/or time factors among otherfactors.

According to an exemplary embodiment, the rate for a flyway segment/zonemay be a product of the number of UAV/drone craft in the flywaysegment/zone (e.g. occupancy); referring to FIGS. 33A/B-34A/B and48A/B-49A/B, the system may charge a higher rate for transit in alower-occupancy lane (e.g. lane E in FIG. 48A/B) than for transit in ahigher-occupancy lane (e.g. lane B in FIG. 48A/B). (According to anexemplary embodiment, rates may change dynamically under market forces,e.g. as demand, occupancy/traffic changes during the time of use/accessby a UAV/drone craft to zones/flyway segments in the airspace.)

According to an exemplary embodiment, the size/shape of a zone at a ratemay vary during a time period (e.g. time of day, day of week, etc.);referring to FIGS. 33A/B-34A/B and 48A/B-49A/B, the flyway has multipleflyway segments (e.g. lanes) and at a peak time period (e.g. 8 AM to 5PM on a weekday or etc.) one set of lanes may be reserved for premiumrates (and UAV/drone craft licensed for priority at the premium rate)and one set of lanes open for standard UAV/drone craft traffic; in theoff-peak time period all sets of lanes may be open to UAV/drone craft ata standard rate (e.g. standard license/priority rights). According to anexemplary embodiment, a UAV/drone craft may obtain (e.g. purchase bylicense, bid/auction, etc.) a “good to go” priority status in theairspace entitling it to operate with a priority over any otherUAV/drone craft (at lower priority status/license rights) on any flywaysegment in any zone at any time; such UAV/drone craft would have flywaysegments/zones on its route cleared of any obstructing UAV/drone craft(if any) by the system.

According to an exemplary embodiment, in a dynamic transaction, a craftcould obtain such priority status (e.g. by purchase, bid/auction, etc.)to execute an urgent mission in the airspace (e.g. special/expediteddelivery), a UAV/drone craft operator could resell such priority statusin a secondary market. According to an exemplary embodiment, the systemcould conduct periodic (e.g. daily, weekly, etc.) sales or auctions forsuch priority status and/or other license rights as to allow UAV/dronecraft to reserve status or bid for enhanced/necessary status inreal-time and/or near the time of a mission to facilitate by marketforces efficient use/operation of the airspace. According to anexemplary embodiment, license rights may be obtained by UAV/drone craftfor short or longer term periods of time (e.g. single mission, period ofa minute or minutes, period of an hour or hours, part of a day, fullday, multi-day, week, month, year, time of year, season, conditions,events, etc.); UAV/drone craft in regular or routine/scheduled operationin the airspace may obtain rights/license fit to the regular/routineduty or operation of the UAV/drone craft. According to other exemplaryembodiments, a UAV/drone craft can transact for an option for futurerights for operation within an airspace; such an option can tentativelyreserve rights for a future date; such optional rights can then beupgraded to a firm reservation at a designated future date; can allowthe option holder to match any future offer for the rights from anotherUAV/drone craft, etc.

According to an exemplary embodiment, the system may providecommunications as to license/rights and route/zone/flyway segmentavailability for UAV/drone craft to use in flight/mission planning;using data analytics the system may provide or facilitate predictivemethods of estimating availability of priority rights/license statusand/or to set rates for use/access of zones/flyway segments in theairspace based on estimate of occupancy/traffic or demand and supply ofpriority rights/license status by UAV/drone craft.

According to an exemplary embodiment, the rate charged to a UAV/dronecraft will be based on the use of the airspace by the UAV/drone craft inthe conditions (e.g. environmental conditions, traffic, etc.) in view ofthe status of the UAV/drone craft (e.g. as the forms of the transactionand/or license of the UAV/drone craft). Use of the airspace willcomprise the time the UAV/drone craft is in the airspace as well as thezones and/or flyway segments in which the UAV/drone craft has traveledin the airspace; as indicated, determination of use may be time-weightedas a product of the time in each zone/flyway segment and a rate appliedfor each zone/flyway segment. Data sources (e.g. data from themonitoring system, from the UAV/drone craft, from external sources,etc.) may provide data as to the location and/or path of travel of aUAV/drone craft in the airspace with varying degrees of accuracy.According to an exemplary embodiment, rates charged to aircraft may be aproduct of function and/or purpose or equipment of or on the aircraftduring the mission (see, e.g. equipment D on UAV/drone craft in FIG. 3F)(e.g. data relay/transmission, photo/video/imaging, surveillance, radiofrequency (rF) signaling, etc.).

According to an exemplary embodiment, the monitoring system will employtechnology as indicated to detect the position of aircraft in theairspace; the monitoring system may employ multiple and/or redundantsystems/devices and data sources intended to provide enhanced accuracyand efficiency in monitoring of aircraft in the airspace (e.g.transponder data verified by GPS tracking data, photographic dataverified by tracking code/checkpoint detectors, video monitoringverified by wireless data transmission, radar, lidar, etc.). Accordingto an alternative embodiment, the monitoring system may employ numericalmethods (e.g. probabilistic/estimates) in an effort to improve accuracyand efficiency in monitoring of aircraft; for example, the system mayuse tracking data and numerical methods to make determinations of zoneor lane positioning of craft using proximity to perimeter (orcenterline) data correlated to zone or lane positions (e.g. calibratedpositions) in the airspace (e.g. basing the determination of locationand rate for aircraft on percent variation from calibratedperimeter/position data for zones or lanes in the airspace.

According to an exemplary embodiment, the system/method may employ anyof a wide variety of methods to determine the rate to be charged anaircraft for use of the airspace (e.g. regions, zones, flyway segments,priority, status, etc.) including methods based on data from datasources and computation methods (e.g. monitoring systems, data sourcesinternal/external to the system/airspace, etc.). For example, the systemmay use a deterministic method based on determination of theroute/location of the aircraft (e.g. zones and flyway segments used)from the monitoring system notwithstanding the margin for error (e.g.possibility/probability that an aircraft was not in the zone/flywaysegment indicated by the monitoring system for some portion of theroute); the system may use a probabilistic method based on aprobability-weighted computation of the route/location of the aircraft(e.g. zones and flyway segments used) in view of data from themonitoring system and assessment of the probabilities of error based onthe detected location and the location/perimeter of zones and flywaysegments (e.g. aircraft detected at or near a perimeter of a zone may beconsidered to be in one zone or another zone based on consideration ofprobabilities and potential error while aircraft detected in or near thecenter of a zone may with greater certainty be considered to be in thezone).

According to an exemplary embodiment, rates charged for an occupancyspace (see generally FIGS. 35 to 49B) may be based on the size of theoccupancy space; for example, a relatively large occupancy space (e.g.with lateral spacing/separation of 0.5 to 1 kilometer or more) will beprovided at a larger relative cost while a relatively small occupancyspace (e.g. with less lateral spacing/separation of several meters ortens of meters up to hundreds of meters) will be provided at a smallerrelative cost. According to an exemplary embodiment, the size/speed andmission/route as well as conditions (e.g. traffic, weather, etc.) forthe UAV/drone craft and other considerations may be used to determinethe proper requested size of the occupancy space.

Monitoring System—Conditions

According to an exemplary embodiment, the system comprises a monitoringsystem that comprises data sources, detectors, etc. to obtaindata/information relating to conditions in the airspace. See FIGS.50-52. As indicated, conditions may comprise environmental conditions(e.g. weather, wind, etc.), events/incidents affecting the airspace,UAV/drone traffic and traffic patterns, etc.; according to any exemplaryembodiment, the system may be configured to monitor any of a widevariety conditions that may exist in the airspace.

According to an exemplary embodiment, the system will usedata/information from the monitoring system and fromnetwork-connected/other data sources (e.g. internal to the system and/orexternal to the system) in the management of the airspace. According toan exemplary embodiment, the monitoring system may use any of a widevariety and/or combination of systems/devices and methods such asdetectors, sensors, antenna, sound/audio monitors/microphones,transponders/transceivers, imaging systems, motion detectors, videocameras/recorders, photo cameras, wireless data links, globalpositioning system (GPS) data, satellite/cellular communication, radar,lidar, data/network communication, instrumentation, recorders, etc.;such systems/device may be installed at or along flyway segments (e.g.including on new/existing structures, buildings, towers, posts/poles,etc.); data sources may comprise UAV/drone craft or systems.

According to an exemplary embodiment, the system will use data from datasources for corroboration, for example, corroborating observed andmonitored weather conditions (e.g. from instrumentation) withnetwork-obtained weather reports (e.g. radar, etc.) for enhancedaccuracy in evaluation/application; for example, observed and monitoredtracking data of a UAV/drone craft (e.g. from digital photographs of anidentifier) may be corroborated by other sensor/detector data (e.g. fromtransponder transmissions from the identifier) and/or with post-missiondata (e.g. network-transmitted GPS data from the craft operator).

According to an exemplary embodiment, the monitoring system will providedata/information as to conditions in the airspace in or near real-timeto be used for continuous and reliable management of the airspace by themanagement system.

Tracking/Monitoring UAV/Drone Craft

According to an exemplary embodiment, the system will be configured totrack and monitor UAV/drone craft in the airspace. As indicated, themonitoring system may be configured to track/monitor UAV/drone craftaccording to any of a wide variety of systems and methods (includingvarious known/conventional methods/systems). See FIGS. 50-52. UAV/dronecraft can be tracked and monitored in the airspace by one or moremethods including sensors, transponders/transmitters, detectors,instrumentation, recorders, imaging, photography, videography, GPS,cellular communications, radar, lidar, motion detectors, sound/audiocapture, wireless data links, data/network communication, etc. See e.g.FIGS. 50-52.

According to an exemplary embodiment, the detector for the system maycomprise any of a wide variety of detector/sensor technologies such asRFID, radar, lidar, imaging, photo, video, motion detection, etc. and/ormay comprise a transponder, transmitter, transceiver, antenna, datalink, etc. As indicated, according to an exemplary embodiment shownschematically in FIGS. 13A/B, 16A/B, 17A/B, 18A/B, 23A/B, 24A/B, 33A/B,34A/B, 35-36, 39-41, 48A/B and 49A, a set or array of detectors D may beinstalled/configured in the airspace to monitor UAV/drone craft in theairspace; as indicated schematically, the monitoring system may employ acombination of systems/devices/detectors of a variety of types in anairspace.

According to an exemplary embodiment, the system may employ a datareporting and collection/analysis system. For example, UAV/drone craftmay upon completion of a mission, upload data from the mission to thesystem for analysis; such data may be used to verify or corroborateother data that the system has collected by other methods (e.g. flightplans and assigned routes in the airspace may also be used by the systemto verify or corroborate other system data for a craft). According to anexemplary embodiment, UAV/drone craft that are equipped to provide(and/or the regularly do provide) accurate data to the system may begiven a discounted rate for registration/licensing. According to anexemplary embodiment, UAV/drone craft and operators that are notauthorized to operate or that operate in non-compliance with applicableprotocol/policies and rules/regulations for the airspace may beidentified by the monitoring system and subject to proper enforcementaction.

According to an exemplary embodiment, the system may employ aircraftsuch as a UAV/drone craft or a balloon (tethered or mobile) that areequipped to travel and track/monitor other UAV/drone craft in theairspace. See e.g. FIGS. 40-41 (monitor UAV/drone craft M patrolling aflyway using monitoring systems such as video recording, etc.).

As indicated schematically in FIGS. 40-41, according to an exemplaryembodiment, a UAV/drone craft M employed for monitoring/tracking (aspart of the monitoring system); UAV/drone craft M may comprise detectors(e.g. such as detectors D at stationary positions along the flyway) andother systems to facilitate data communications and interchange with thesystem. According to an alternative embodiment, UAV/drone craft M mayoperate under the control of an operator affiliated with the system(e.g. able to be dispatched in real time to monitor particularsituations or places in the airspace); UAV/drone craft M may operate ina prescribed/programmed route (e.g. in a specified pattern or “loop”).As indicated, UAV/drone craft M may operate in coordination withdetectors D at stationary positions along the flyway and may be used toconfirm or supplement data from such detectors (e.g. by sensors, orphoto/video camera imaging) and/or may provide a data/communicationslink if needed to UAV/drone craft operating in the airspace (e.g.functioning as a communication relay, wireless access point, etc.).

According to an exemplary embodiment, data and information frommonitoring by detectors and/or UAV/drone craft employed for monitoringcan be used by the system to manage and administrate theairspace/flyways, including to evaluate conditions/traffic and toroute/re-route UAV/drone craft.

According to an exemplary embodiment, the system is able to obtain,corroborate, evaluate and use/apply reliable data/information totrack/monitor the use/access of the airspace in comparison to transactedterms/license and assigned routes/rights and invoice/bill and receivepayment from UAV/drone craft based on actual/accurate data/information.

UAV/Drone Traffic Direction/Control

According to an exemplary embodiment, as indicated schematically inFIGS. 4A through 21B, UAV/drone traffic in an airspace can be routedthrough and along designated flyways and flyway segments inzones/regions in an airspace. According to an exemplary embodiment, asindicated schematically in FIG. 22B, UAV/drone traffic on flyways in anairspace can be routed through and across designated zones in theairspace. As also indicated, flyway segments/zones may comprisedesignated lanes of travel for UAV/drone craft. See, e.g. FIG. 19B.

According to an exemplary embodiment, UAV/drone traffic can be directedin flyways and flyway segments by providing lanes for UAV/drone craft(see e.g. FIGS. 23A/B, 24A to 24C, 27-32, 41A/B, 42A/B and 43) and/or byproviding designated occupancy spaces (or blocks) for UAV/drone craft inflyway segments/lanes (see e.g. FIGS. 33-40, 44-47, 48A/B and 49A/B)(e.g. permitting use of a flyway segment/lane by multiple UAV/dronecrafts with defined spacings). Detectors D (of various types) for themonitoring system may be positioned at various points in the airspace.See e.g. FIGS. 13A/B, 16A/B, 17A/B, 18A/B, 21A/B, 23A/B, 24A/B, 33A/B,34A/B, 35, 36, 39, 41, 48A/B and 49A/B (in airspace) and FIG. 3F (on acraft).

According to an exemplary embodiment, in implementation of the system,each UAV/drone craft will be able to travel through an airspace withminimal delay or disruption according to the rights and restrictions ofthe UAV/drone craft (e.g. relative to other UAV/drone craft). Accordingto an exemplary embodiment, in implementation the system will useplanning and routing to direct UAV/drone traffic in a safe and efficientmanner through and along flyway segments. According to an exemplaryembodiment, the system comprises assignment of routes for UAV/dronecraft in consideration not only of the mission but also ofcapability/type of the UAV/drone craft as well as monitoring ofconditions in the airspace as well as UAV/drone traffic. According to anexemplary embodiment, the designation and establishment of flyways andflyway segments with lanes facilitates the administration and managementof UAV/drone traffic in the airspace by providing corresponding trafficconventions and guidance for operators of UAV/drone craft.

As indicated, the management system in the administration of theairspace may establish maximum and minimum speed/regulated speed limitsfor UAV/drone craft in flyway segments/lanes to ensure efficient trafficflow through the airspace; rates for use of a flyway segment/lane may beestablished with reference to speed limits and other factors such asoccupancy as well as the rights/priority and route assigned to theUAV/drone craft. According to an exemplary embodiment, UAV/drone craftwould be routed by the management system to travel in flywaysegments/lanes according to capability such as speed of travel of theUAV/drone craft.

Referring to FIGS. 23A and 23B, flyway segments with multiple lanes forUAV/drone craft are shown schematically. The flyway segment of FIG. 23Aprovides three lanes each separated by a gap G monitored by a set ofdetectors D; separate outward lanes FS and FN are for transit each in asingle direction; a central undesignated lane FU is available to operatewith transit in either direction as may be decided by the system in viewof conditions (including UAV/drone traffic congestion, eventrequirements, time of day, special reservation, etc.). For example, iflane FN is congested, travel in the undesignated lane FU may be directedto flow in the same direction as travel in lane FN for a time period;UAV/drone craft in lane FN may be directed into lane FU for the timeperiod to relieve congestion in lane FN; travel in lane FS isunaffected. As indicated, if lane FS is congested the same method can befollowed for a time period to use lane FU to relieve congestion in laneFS. See also FIGS. 28 and 29. FIG. 23B shows a flyway segment operatingon the similar principle but comprising additional lanes (e.g. toaccommodate different UAV/drone crafts; for example of different type,control, size, capability, speed, etc.). High speed/capability UAV/dronecraft may travel in one lane or set of lanes; low speed/capabilityUAV/drone craft may travel in a separate lane or set of lanes.

FIGS. 24A, 24B and 24C show schematically other arrangements of a flywaysegment as can be configured. For example, a flyway segment is shown inFIG. 24A with multiple lanes that are established for unidirectionaltravel (e.g. lanes FB and FC) and a lane that can be configured fortravel in each direction for a period of time (e.g. lane FA) (compareFIG. 24C); a flyway segment is shown in FIG. 24B with all lanesproviding travel in the same direction.

The safe and efficient operation of multiple aircraft in an airspacerequires that the possibility or risk of collisions between aircraft beminimized if not eliminated. Systems and methods for avoiding collisionsin an “open” airspace between manned aircraft are known and implementedby air traffic control systems around the world on a daily basis formanned aircraft. Known systems for facilitating collision, detection andavoidance for aircraft employ intervention measures, communicationsbetween aircraft operators, evaluation of flight plans/trajectories,etc. and other methods (that tend to be more suitable for aircraft thatcomprise control systems/communication systems with sufficientcapability). See e.g. U.S. Pat. No. 8,082,102 and WIPO Publication No.2013/014646 A1. See also U.S. Pat. No. 8,368,584 and FIG. 25.

According to an exemplary embodiment, the system and method of managingan airspace by systematically establishing designated flyways with lanesand/or spaces for UAV/drone traffic by reference over features in thezone/region (as indicated schematically in FIGS. 4A through 21B) is ableto reduce the risk of collision of UAV/drone craft in the airspacenotwithstanding that the airspace may be occupied with a wide range ofdifferent UAV/drone craft having a wide range of control systems andcapabilities (e.g. from superior to marginal in performance). Accordingto an exemplary embodiment, as indicated in FIGS. 23A-24C and 26 to 35,by designating lanes for travel/transit of UAV/drone craft the systemand method is configured to establish standards includingprotocols/policies rules/regulations, conventions and practices for safeand efficient operation of UAV/drone craft in the airspace.

As indicated schematically in FIG. 26 (and in contrast to FIG. 25), theestablishment of designated lanes for UAV/drone craft operating in aflyway permits separation of the lanes (including for UAV/drone crafttraveling in opposite directions) by a horizontal offset X and avertical offset Y; offsets X and Y (e.g. forming a gap between lanes)may be specified and implemented according to factors relevant tooperator of the airspace (e.g. including but not limited to the type andcapability of the UAV/drone craft, the control/communication systems,the monitoring systems, etc.). Referring to FIGS. 27 and 30, lanes in aflyway segment may be positioned so that opposing direction UAV/dronetraffic is separated in a horizontal (side-by-side) arrangement;referring to FIGS. 29 and 31-32, lanes in a flyway segment may bepositioned so that opposing-direction UAV/drone traffic is separated ina vertical (above-the-other) arrangement. As indicated schematically inFIG. 28, the flyway may comprise a passing lane in which UAV/craft inoperation in either direction may temporarily enter to overtake aslower/disabled/obstructing UAV/drone craft.

According to an exemplary embodiment, designation of lanes andinterchanges is configured so that there is reduced risk of unintendedinteraction between UAV/drone craft and reduced risk of collisions byUAV/drone craft. See FIGS. 33-34. Protocol and convention for UAV/dronecraft operation would prescribe spacing/separation between UAV/dronecraft operating in the same flyway lane (as indicated in the FIGURES);offset and gaps between lanes would prescribe spacing/separation betweenUAV/drone craft in different flyway lanes (e.g. regardless of thedirection of travel). According to an exemplary embodiment, flywayconfigurations with landing/waiting areas and high-speed lanes and/ormultiple/passing lanes for UAV/drone craft may be provided. See e.g.FIGS. 23A-24C, 28 and 33A-35.

Referring to FIGS. 33A/B and 34A/B, configurations for lane arrangementsand interchanges between flyway segments of an airspace are shownaccording to exemplary embodiments (e.g. such as to allow UAV/dronecraft to change from one flyway segment to another during transit in theairspace); according to an exemplary embodiment, protocol/rules forinterchanges may be established by the management system within theadministration function. See also FIGS. 4B, 5B and 48A/B and 49A/B.

As indicated schematically in FIGS. 27 through 35, each UAV/drone craftwould be traveling in a designated lane in the flyway as assigned by thesystem with the UAV/drone craft registered to enter the airspace.According to an exemplary embodiment, the travel of each UAV/drone craftin each lane would be regulated and tracked/monitored. Management andcontrol of the flyway according to an exemplary embodiment would alsocomprise the direction and diverting or grounding of UAV/drone craftthat become disabled or do not comply with regulations/rules for transitor operator in the flyway/airspace. As UAV/drone craft exit flywaysegments/lanes openings are created for other UAV/drone craft to enter.See FIGS. 33A/B, 34A/B and 35 (also indicating a parking landing lot orstation T with system P to provide services).

Referring to FIGS. 36 to 42, according to an exemplary embodiment, eachUAV/drone craft may be assigned by the system to operate in a designatedoccupancy space (e.g. block or volume) within a flyway segment or lane.As indicated schematically, the size and shape of the occupancy spacefor a UAV/drone craft can be configured in consideration of the type,control, size, capability, speed, etc. of the UAV/drone craft as well asother factors. See e.g. FIGS. 37, 40-41. In operation, each UAV/dronecraft would be expected to maintain position within the occupancy spacethrough the flyway and airspace; no other UAV/drone craft would bepermitted to enter the occupancy space of another UAV/drone craft; asone UAV/drone craft exits an occupancy space in the flyway/lane, anopening is created for another UAV/drone craft to enter. See FIG. 36(also indicating a parking/landing lot or station T with system P toprovide services). Referring to FIGS. 48A/B and 49A/B, configurationsfor lane arrangements and interchanges between flyway segments of anairspace are shown according to exemplary embodiments.

Rates for an occupancy space could be determined by the size/shape andspeed/route of the occupancy space through the airspace according to anexemplary embodiment; maximum and minimum speed/regulated speed forUAV/drone craft may be established in lanes with occupancy spaces toensure efficient traffic flow through the airspace.

As shown schematically according to an exemplary embodiment in FIGS. 37and 40-41 occupancy spaces may be configured in a variety of shapes andsizes and to accommodate UAV/drone craft of a variety of types and sizesand/or routes and missions on flyway segments in or through an airspace.As indicated in FIGS. 39, 40-41, occupancy spaces in a flyway lane F mayinclude a single UAV/drone craft such as UAV/drone craft W and UAV/dronecraft Z in spaces S in FIG. 39 or multiple craft such as two UAV/dronecraft Z in space S in FIG. 40. Spaces S may be sized to a standard sizeand/or with progressively larger sizes as indicated in FIG. 40.Occupancy spaces may be provided in multiple (opposing direction) lanesas shown schematically in FIG. 41.

According to an alternative embodiment, an occupancy space that wasassigned to an operator may be used for multiple UAV/drone craft at thedirection of the operator and/or subdivided for occupancy by multipleUAV/drone craft. See FIGS. 42-47. As shown schematically in FIGS. 42 to45, an operator may divide an occupancy space for various arrangementsof UAV/drone craft. See also FIGS. 46A-47. As shown schematically inFIGS. 46A/B and 47, an operator may use an occupancy space for squadronof UAV/drone craft operating in a formation (e.g. under thecontrol/command of a lead UAV/drone craft or under another method ofcontrol).

As indicated schematically in FIGS. 44-45 and 47, the flyway maycomprise a utility lane that be used, for example, for UAV/drone craft Memployed by the system to monitor UAV/drone traffic and conditions inthe airspace (or for disabled UAV/drone craft to be moved out of primarytraffic lanes for UAV/drone craft in operation).

Parking/Landing/Service Stations

As indicated schematically in FIGS. 4A/B, 9A/B, 21A/B and 35-36, thesystem may provide stations T along flyways in the airspace to be usedby UAV/drone craft for parking/landing and/or for provision of servicessuch as refueling/recharging or maintenance/inspection (or for landingof malfunctioning or disabled UAV/drone craft). As indicated in FIG.21B, stations may be configured to provide shelter for UAV/drone craftfrom conditions (e.g. rainstorm O approaching the flyway). As indicatedin FIGS. 35-36, stations may be configured to facilitate management ofthe airspace (e.g. by providing a landing/parking area for UAV/dronecraft that are required to exit a flyway to give way to higher-priorityUAV/drone craft).

According to an exemplary embodiment referring to FIG. 35, a lane of aflyway segment F is shown schematically along with station T shown as anadjacent waiting/parking lot or pad L for UAV/drone craft. As indicatedschematically, UAV/drone craft are traveling in the flyway lane F;UAV/drone craft Y is exiting the flyway lane F to join UAV/drone craftin the lot L as UAV/drone craft X is entering the flyway lane F to joinUAV/drone craft W and UAV/drone craft Z in transit.

According to an exemplary embodiment referring to FIG. 36, a lane of aflyway segment F is shown schematically with station T shown as anadjacent waiting/parking lot or pad L for UAV/drone craft. As indicatedschematically, UAV/drone craft are traveling in occupancy spaces S inthe flyway lane F; UAV/drone craft Y is exiting the occupancy space S inthe flyway lane F to join UAV/drone craft P in the lot L as UAV/dronecraft X is entering the occupancy space S in the flyway lane F to joinUAV/drone craft W and UAV/drone craft Z in transit.

The station may be configured for one type or a variety of types ofUAV/drone craft that may have a variety of requirements (e.g. forlanding/take-off); for example, the station may provide runways forUAV/drone craft or may be configured in a more compact arrangement forvertical take-off/landing craft (see FIGS. 4A/B-5A/B and 9A/B).

As indicated schematically in FIGS. 21A/B and 35-36, the station mayalso provide a system P for providing services and utilities forUAV/drone craft that have landed at the station; for example, aUAV/drone craft that is disabled may obtain an inspection or service; aUAV/drone craft may exit to a station and use the system forrefueling/recharging; a UAV/drone craft may exit and use the system atthe station to establish a reliable data link to the management systemand/or an operator; a UAV/drone craft may use the system/station toconduct a transaction with the management system (e.g. adjustment orroute or rights/license, etc.).

According to a preferred embodiment, the management system may operateor contract with third parties to operate stations to provide services,parking, etc. for UAV/drone craft at stations in commercialtransactions; according to an exemplary embodiment, UAV/drone craft maytransact/license with the system to have access to stations in theairspace and/or for services, parking, etc. at transacted rates (e.g.billed/invoiced to the UAV/drone craft after completion of a mission inthe airspace).

Management System/Subsystems and Functions

According to an exemplary embodiment, the system for management of anairspace will comprise subsystems such as a computing system, monitoringsystem, data/network systems, etc. See e.g. FIGS. 50-60. Referring toFIGS. 50-60, technical/computing and data/network functions comprisingthe system for managing an airspace for UAV/drone craft are shownschematically according to an exemplary embodiment.

As shown in FIG. 50, according to an exemplary embodiment, the systemcomprises a set of subsystems that are connected by a network (or set ofnetworks). According to an exemplary embodiment, the system isimplemented using conventional computing and network technology, forexample, as disclosed in U.S. Patent Application Publication No.2008/0072284 (incorporated by reference). See also FIG. 53 (schematicblock diagram of representative computing system) and 54 (schematicblock diagram of representative network system). As indicated in FIGS.50 and 57-60, according to an exemplary embodiment, the system comprisesa management system for the airspace and a control system for theairspace.

As also shown schematically in FIGS. 57-60, according to an exemplaryembodiment, the management system (see FIG. 57) comprises anadministration module/system (see FIG. 59) and a control module/system(see FIG. 60) in operation to perform a set of basic functions (e.g.planning/management, control/direction, administration, monitoring,communication/reporting, billing, etc.) (see FIG. 58). According to anexemplary embodiment, the management system comprises a computing system(see FIG. 54) configured by control programs/algorithms with aflyway/routing function and a license/rights administration function.According to an exemplary embodiment, the control system comprises acomputing system (see FIG. 54) configured by control programs/algorithmswith a real-time UAV/drone craft/conditions monitoring function and areal-time flyway management function. As indicated, when a UAV/dronecraft (e.g. with a mission/plan) registers with the system to operate inthe airspace the management system determines and assigns a route alongflyway segments/zones in the airspace and determines licenserights/rates for the UAV/drone craft to operate in the airspace; whenthe UAV/drone craft initiates the mission in the airspace the controlsystem monitors (and directs) the operation of the UAV/drone craft(including real-time communication and/or control); when the mission iscompleted/terminated the management system collects/validates data fromthe UAV/drone craft and verifies the rate/billing for use of theairspace.

The system uses data from data sources (e.g. external and/or monitoredin the airspace such as from detectors, monitor craft, etc.). Storeddata and control programs/algorithms used by the system to performfunctions (see FIG. 58) are available to the system by network/dataconnection. Data for the airspace such as designated flyways,flyway/route segments, flyway lanes, protocol and rules, maps,obstructions, hazards, etc., is maintained as stored data for the system(updated as needed). See also FIG. 61 (UAV/drone craft data sets). (Asindicated, the system may also provide a data analytics function thatcan be used to modify operating/control programs and algorithms, toenhance functionality/efficiency, to share/commercialize data sets,etc.)

According to an exemplary embodiment, the system is able to operateusing known/conventional and future/compatible subsystems of technology(e.g. computer systems, computing devices, network/data communications,etc., structured/integrated (see FIGS. 50-56) and configured/programmed(see FIGS. 57-60) to perform functions as shown/indicated to manage anairspace for UAV/drone craft. As indicated schematically in FIGS. 50 and56, the system may be linked to other systems/networks including theinternet (and thereby connected to additional data sources and othercomputing/data and communication devices).

As shown schematically in FIGS. 50-51 and 58 the system is configured tomanage/administrate the airspace and UAV/drone craft that comprises theUAV/drone traffic in the airspace and to perform associated functions(see FIGS. 57-60) including to monitor and evaluate conditions in theairspace. According to an exemplary embodiment, the system comprises amonitoring system (e.g. comprising a set of detectors such as sensors,monitors, systems, devices, instrumentation, receivers, transceivers,antenna, etc.) configured to provide data on conditions in the airspaceincluding UAV/drone traffic, environmental conditions/weather, etc. SeeFIGS. 16A/B and 21A/B and 51. According to an exemplary embodiment, thesystem is in data communication with UAV/drone traffic (e.g. via UASoperators, network connection and/or monitoring system). According to anexemplary embodiment, data from other/external sources available to thesystem may provide information that can be used to confirm/verify orvalidate/corroborate conditions monitored in the airspace or to thesupplement data from the monitoring system to facilitate operation ofthe system; data provided by UAS operators and/or other sources can beused to maintain records related to UAV/drone craft for purposes ofregistration (e.g. craft identity, type, rights, etc., operatoridentity, mission data, routes, rates, events, etc.); data reported byUAS operators and/or UAV/drone craft can be used by the system tomonitor and/or to manage and administrate the airspace (e.g. data fromoperator of route/GPS data, etc. after a mission is completed by acraft). As indicated schematically, data may be shared and interchangedby the system with UAS operators and other authorized users/systems tofacilitate management/administration and monitoring/operation of thesystems. According to an exemplary embodiment, the monitoring system maybe linked to other monitoring systems such as traffic cameras, etc.

Referring to FIG. 51, according to an exemplary embodiment, themonitoring system is shown schematically with connectivity to datasources/systems providing data as to UAV/drone craft (e.g. via themanagement/control system) and conditions (e.g. via detectors, etc.).The monitoring system is configured to provide the system withdata/information on conditions in the airspace including, for example,environmental/weather conditions, events, alerts, hazards, etc. whichmay be used to manage and administrate UAV/drone traffic in theairspace. The monitoring system may receive data from detection (e.g.monitors/detectors, camera/video/imaging, sensors/RFID, etc.), tracking(e.g. radar, GPS/satellite, cellular tracking, etc.), communications(e.g. radio/radio frequency, antenna/broadcast, data link, datacommunications, etc.), telemetry (e.g. receivers/transceivers) or anyother systems (presently known or future implemented). As indicatedschematically in FIG. 21A/B a detector D associated with a station Tand/or installed with or adjacent to a service, system P may beconfigured to provide tracking/monitoring of craft UAV as well astracking/monitoring of conditions such as weather/storm O. According toan exemplary embodiment, the system comprises a monitoring systemconfigured to facilitate the acquisition and evaluation of timely andaccurate data/information from multiple types of data sources. Themonitoring system may receive data from network-available sources (e.g.other network devices and data storage, internet-connected sources, LANsources, intranet sources, etc.) and other data sources (e.g. of anykind); such data may include background data such as time/date, events,reports, etc. Also available to the monitoring system from themanagement/control system may be information/data from UAV/drone craftin operation in the airspace or registered/identified to the system;such data for a UAV/drone craft may include identity/operator, statusand condition, state and configuration, capability, license rights/rate,etc. (Data may be communicated directly from UAV/drone craft oroperators such as monitoring craft M shown schematically in FIGS.40-41.)

Referring to FIG. 52, the monitoring system connected to UAV/dronetraffic is shown schematically according to an exemplary embodiment. Asindicated, a UAV/drone craft operating in the airspace may be under thedirect control of an operator, may be deployed into the airspace with aflight plan/program, may be under the control of a squadron leader (seeFIG. 46A/B), may be part of a fleet, may be operating autonomously, etc.According to an exemplary embodiment, the system is configured tomanage/administrate the airspace for any suitable type of UAV/dronecraft (e.g. subject to controllability/airworthiness requirements).UAV/drone craft and/or operators of individual or multiple UAV/dronecraft will interact by data communication with the system by networkand/or by the monitoring system. As indicated, network-transmitted data(e.g. in real-time or post-mission) to the system from a UAV/drone craftor operator may be used to validate/correct/confirm data that has beenobtained by the system from the monitoring system. For example, if adetector (such as a camera or transponder or toll/fare meter) indicatesthat a UAV/drone craft has been in a particular flyway segment in aparticular zone at a particular day/time during a mission, a data upload(such as GPS track) from the UAV/drone craft or operator after themission can be used to confirm that the UAV/drone craft was accuratelydetected in the airspace.

As shown schematically in FIGS. 55 and 56, according to an exemplaryembodiment, the system as well as various subsystems and (registered)UAV/drone craft, UAS operators/pilots, service centers, office staff,etc. may be connected by network and able to share/transmitdata/information. As indicated schematically in FIGS. 53 and 56,UAV/drone craft may be configured to communicate directly with a network(and therefore to the system and or monitoring system) or via a UASoperator by data link (and by the operator/pilot to the system and/ormonitoring system via the network). According to any preferredembodiment, the system is able to monitor UAV/drone craft and UAV/dronetraffic in the airspace essentially in real-time in a reliable manner(as indicated).

As indicated in FIGS. 50, 55-57 and 60, according to an exemplaryembodiment, certain UAV/drone craft by network and/or by operator may bein real-time communication with the system and able to bedirected/controlled as to operation/routing in the airspace during amission (other types of UAV/drone craft may operate with lessor orvirtually no control once deployed in the airspace). A UAV/drone craftthat is configured to be in communication/control with the system(directly or by operator) during a mission in or through the airspacemay be provided with the capability to modify or adjust the route and/orrate for travel/passage through flyway segments/zones in the airspace(e.g. capability for dynamic transactions with the system during amission).

As indicated in FIGS. 50, 55, 56 and 57 data communications may beestablished between the system by network with UAV/drone craft,operators and other authorized systems/persons/entities.

Referring to FIGS. 61, 62 and 63 data sets and functionality forregistration and management of UAV/drone systems (UAS) and UAV/dronecraft for operation in the airspace are shown schematically according toan exemplary embodiment. As indicated in FIG. 61, at the time ofregistration, a UAV/drone craft will be identified and given a profile(data file with identity, billing information, etc.); conditions(flyways/traffic, operating, environmental, etc.) in the airspace andstate/status of the UAV/drone craft will be assessed; licenserate/priority of the UAV/drone craft will be determined and registered;the duty (mission) will be registered and a route available on flywaysegments/zones for the mission in the airspace will be assigned by themanagement system.

As indicated in FIG. 62, the UAS/operator will provide information forthe system as to identity/registration of craft/mission, licenserights/rate, craft type/configuration, control/management system forcraft/operator, status/condition of craft, telemetry/data from thecraft, operator history, other data communications.

As indicated in FIG. 63, each UAV/drone craft in operation in theairspace registered with the system will provide craft information (e.g.identification, type, condition, capability, state/status, operationmode, operation history) as well as license rights (rate) informationand flight plan/route (mission) information to the system by datacommunication (e.g. before and/or during and/or after missions).

Dynamic Transactions—System/Craft

According to an exemplary embodiment, the system and UAV/drone craftwill be configured to conduct transactions of various types such asregistration and billing/payment; according to another exemplaryembodiment the system and UAV/drone craft may be configured to conduct“dynamic” transactions (e.g. transactions occurring during the missionof the UAV/drone craft in the airspace or otherwise while the UAV/dronecraft is in active operation in the airspace). (A “static” transactionwould be a transaction occurring before the UAV/drone craft hasinitiated the mission in the airspace, e.g. when the UAV/drone craft isnot in active operation in the airspace on the mission.)

According to an exemplary embodiment, the UAV/drone craft may beprovided with the capability of conducting a dynamic transaction withthe management system by any of a variety of communications including bydata/network connection, by direct communication (e.g. through a directdata connection with the management system and/or through the monitoringsystem/detectors, through the pilot/operator of the UAV/drone craft) andby messaging/communication over other networks (e.g. direct connection,network connection, messaging/cellular link, etc.). See FIGS. 3F, 19Band 50-63.

A dynamic transaction may comprise any of a variety of transactionsbetween a UAV craft/operator and the system, including for examplemodification of/modifying a route, considering modification of/modifyinga route (e.g. upgrading or downgrading rights/privileges), obtainingdifferent license rights/privileges, etc. According to an exemplaryembodiment, a dynamic transaction may comprise participation in anauction or bid process, supplemental payment (e.g. to pay for an upgradeof rights/priority), refund of fee/rate (e.g. after a downgrade ofrights/priority).

Process/Operation of Management System

Referring to FIGS. 64-75, processes for management of the airspace areshown schematically according to exemplary and alternative embodiments.According to an exemplary embodiment, the processes for management (e.g.administrator and control) may be operated on a computing system of thetype shown in FIG. 54 (among other systems) and/or by a system of thetypes shown in FIGS. 50-60 (among other systems) in an airspace of thetypes shown in FIGS. 4A to 22B (among other airspaces) with UAV/dronecraft of the type shown in FIGS. 1-3F (among other craft). According toan exemplary embodiment, the process is configured to implement somecombination of functions and features of the system formanagement/administrator and control as indicated schematically in FIGS.57-60 for UAV/drone craft and UAV/drone craft providing some combinationof sets of data/information as indicated schematically in FIGS. 61-63.According to an exemplary embodiment, the process is configured so thatUAV/drone craft can operate in flyways/zones of an airspace as indicatedschematically in FIGS. 4A through 49B.

According to an exemplary embodiment, UAV/drone craft will register withthe system by providing certain information (e.g. to establish identityand a profile, see FIG. 61); UAV/drone craft will also register amission (e.g. flight plan, destination/purpose, etc.) with the system.According to an exemplary embodiment, registration with the system willrequire data interchange between the system and the UAV/drone craftand/or operator.

As indicated schematically in FIGS. 50-52, according to an exemplaryembodiment, the system will obtain data from various data sources (e.g.data storage/history, UAV/operator profiles, detectors, network/dataconnections to UAV craft/operators, commercial/public databases, GPStracking, network/data connectors to other sources, internet resources,etc.) to be used in the management/administration and control of theairspace/flyway and otherwise in the operation of the system.

As indicated, data including UAV/drone craft profile, mission/plan/routedata, conditions, traffic, etc. will be used by the system to determinerates for use/access, priority, etc. for UAV/drone craft in transit inthe airspace. See FIGS. 61-63. According to an exemplary embodiment, atransaction with the system (e.g. registration, licensing, payment,etc.) will occur as a precondition to the UAV/drone craft havingauthorized use/access to the airspace.

As indicated in FIGS. 64 to 75, the process of management (e.g.administration and/or control) of an airspace for operation of UAV/dronecraft in the airspace is shown schematically and representationallyaccording to an exemplary embodiment and alternative embodiments. (Theprocesses are representative examples that indicate generally andspecifically functions and features of the system; as indicated,according to other exemplary embodiments and alternative embodiments,the system may implement and use other processes that follow other stepsor sequences of steps.)

As shown schematically in FIGS. 64-81C, a process of administrating andmanaging the transit/passage of a UAV/drone craft through the airspaceunder administration and management of the system will comprise aninitial transaction with registration and evaluation of the craft andthe mission of the craft (e.g. a transaction between the craft/operatorand the system). According to a preferred embodiment, the craft/operatorwill establish an account with the system to facilitate transactionssuch as financial transactions and a data/network connection with thesystem to facilitate data communications/commands during use/access bythe craft to the airspace managed by the system. For example, thecraft/operator may use a financial account (e.g. credit/debit cardaccount, bank account, etc.) for financial transactions with the system.(According to any preferred embodiment, financial transactions with thesystem may be conducted using known/present conventional and/or anyfuture methods of conducting such transactions.) As indicated, accordingto any preferred embodiment, any invoicing/billing discrepancies intransactions with the system relating to a mission by a craft in theairspace may be addressed and resolved after the mission between thecraft/operator and system using data that has been obtained/recordedduring the mission.

General System Operation (FIG. 64)

Referring to FIG. 64 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 64 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes.

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Maintain Clear Route (FIG. 65)

Referring to FIG. 65 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 65 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission, to be performed by the craft in theairspace, is concluded; communication by the system (e.g. ofdata/information such as traffic, conditions, alerts, etc.) with thecraft/operator during the mission facilitates performance of the missionby the craft in the airspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, tomaintain a clear route for the craft to complete the mission in theairspace (e.g. by routing/re-routing other craft of lower priority inaccordance with the priority/rights obtained and assigned for thecraft). As indicated schematically in FIGS. 33A/B-34A/B, 35-36,48A/B-49A/B, a lower-priority craft that may be a potential obstructionto a higher-priority craft may be directed to move to another flywaylane or to reroute to another flyway segment or to exit the flyway togive clearance to the higher-priority craft.

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Dynamic Rate Adjustment (FIG. 66)

Referring to FIG. 66 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 66 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace). As indicated, the transactionmay permit dynamic transaction (pricing) of the rate to be paid by thecraft for use/access to the airspace (e.g. rates that may increase ordecrease as a function of time, traffic, other conditions).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, where thesystem and craft are configured for dynamic transaction (e.g. pricing)the monitored conditions in the flyway (e.g. a flyway segment orzone/region) may result in corresponding monitored adjustment of therate applicable to the craft under the conditions in the airspace (e.g.rates increase for transit in peak time periods or high traffic volumeconditions and rate decreases in off-peak time periods).

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator).

System Operation—Route Availability (FIG. 67)

Referring to FIG. 67 according to an exemplary embodiment, a process formanagement/administration of an airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 67 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace if a proposed route is available for the craft. As indicated,if the proposed route is unavailable for the craft the craft/operatorwill be informed and may be able to approve/adjust the route and to makeany required adjustment of route/flights so that any potentiallyobstructing craft on the route is rerouted.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. (As indicated, if the craft hasobtained appropriate priority rights potentially obstructing craft willhave been routed/re-routed to clear the route for the craft.)

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Re-route Obstructing Craft (FIG. 68)

Referring to FIG. 68 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 68 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace). As indicated, the craft hasobtained a license/rate that provides priority over potentiallyobstructing craft along the route.

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, anypotentially obstructing craft on the route of the craft will bererouted.

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Maintain Rate/Dynamic (FIG. 69)

Referring to FIG. 69 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 69 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, ifconditions develop in the airspace that require a dynamic transaction(e.g. rate adjustment or rerouting, priority conflict with other craft,etc.) the craft/operator will be given an opportunity to adjust/increasethe rate and maintain the rate with rate adjustment or to maintain therate and adjust the route (e.g. to a route where the rate is applicableor where the craft is not an obstruction to a higher-priority craft).

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Maintain Rate/Dynamic (FIG. 70)

Referring to FIG. 70 according to an exemplary embodiment a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 70 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction (e.g. pricing/rates) with the system and/or with andautonomous/on-board control function (e.g. with appropriatetelemetry/data communications) intending to perform a proposed missionin the managed airspace, such as delivery of a parcel/payload to alocation in the airspace and/or passage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, ifconditions develop in the airspace that require a dynamic transaction(e.g. rate adjustment or rerouting, priority conflict with other craft,etc.) the craft/operator will be given an opportunity to maintain theroute with rate adjustment or to maintain the rate and adjust the route(e.g. to a route where the rate is applicable or where the craft is notan obstruction to a higher priority craft).

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Adjust Rights/Dynamic (FIG. 71)

Referring to FIG. 71 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 71 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, conditionsmay develop in the airspace or otherwise for the craft/operator thatcause the craft/operator to consider adjustment of rights/priority (e.g.upgrade for higher rate or downgrade for lower rate); the craft/operatormay, as indicated, (e.g. an alternative) to make an adjustment of theroute (e.g. to a route where the conditions allow suitable passageand/or the craft is free of obstruction as a higher priority craft) orto maintain the route with higher priority/rights (e.g. priority on theroute over potentially obstructing craft).

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Rate Adjust Condition (FIG. 72)

Referring to FIG. 72 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 72 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, conditionsmay develop in the airspace that would cause a dynamic transaction inthe form of a rate adjustment (e.g. increase) for the craft/operator.The craft/operator may approve adjustment of the rate and maintain theroute. The craft may maintain the route at higher priority/rights (e.g.priority on the route over potentially obstructing craft). Thecraft/operator may as indicated, (e.g. an alternative) discontinue themission or revise the route (e.g. to a route where the craft hasappropriate rights/priorities for transit at the rate).

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Route Adjust Condition (FIG. 73)

Referring to FIG. 73 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 73 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, conditionsmay develop in the airspace that would cause a dynamic transaction inthe form of a route adjustment for the craft/operator. Thecraft/operator may approve adjustment of the route and maintain theroute. The craft may maintain the route at higher rate (e.g. higherpriority on the route over potentially obstructing craft). Thecraft/operator may as indicated, (e.g. an alternative) discontinue themission; as indicated, if the route is adjusted/revised the mission willcontinue.

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Rights Adjust/Dynamic (FIG. 74)

Referring to FIG. 74 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 74 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, conditionsmay develop in the airspace or otherwise where the craft/operatorconsiders an adjustment of rights. The craft/operator may approveadjustment of the rate and continue the route with higherrights/priority (e.g. priority on the route over potentially obstructingcraft). The craft may consider an adjustment of the route (e.g. to aroute where the craft is a higher priority craft). The craft maymaintain the route without adjusting rights.

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

System Operation—Obstructing Craft/Priority (FIG. 75)

Referring to FIG. 75 according to an exemplary embodiment, a process formanagement/administration of airspace and UAV/drone craft by a systemusing data/data communications is shown schematically. The processindicated schematically in FIG. 75 may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransaction with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) todetermine the license/rights and fee/rate to be applied for use/accessby the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; a route (e.g. proposed flywaysegments and zone/region access/use timing) is assigned by the system tothe craft for the mission and communicated to the craft/operator.

Registration of the craft and mission by the system informs the systemof relevant conditions in the airspace (e.g. traffic/status,environmental conditions/weather, events/situations, potentialobstructions/alerts, etc.) to be evaluated to facilitate assignment andapproval of an appropriate route and rights to the craft for the missionincluding a determination and application of appropriate license/rightsand the proper fee/rate to be assessed to the craft/operator to performthe mission in the airspace; communication to the craft/operatorfacilitates initiation by the craft/operator of the mission in theairspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis concluded; communication by the system (e.g. of data/information suchas traffic, conditions, alerts, etc.) with the craft/operator during themission facilitates performance of the mission by the craft in theairspace.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace); data from tracking/monitoring may also be communicated to thecraft/operator for other purposes. For example, as indicated, apotentially obstructing craft may be identified on the route; if thecraft has priority/rights over the potentially obstructing craft, thepotentially obstructing craft will be rerouted and the craft maycontinue on route. If the potentially obstructing craft haspriority/rights over the craft, the craft will be rerouted and assignedan alternative route. Alternatively, the craft may purchase or bid onpriority rights in a dynamic transaction. (As indicated, alternativelythe route adjustment may comprise a temporary landing or delay; thecraft may, after the delay, return to the flyway/route.)

Upon completion by the craft of the mission in the airspace, datacollection and analysis (e.g. analysis of data collected during themission and/or of data obtained from the craft/operator and/or othersources during and/or after the mission) is conducted and completed bythe system to facilitate a post-mission corroboration/determination(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace) and application ofthe fee/rate to be assessed to the craft for the detected/actualuse/access to the airspace by the craft during the mission;communication/notice to the craft/operator may comprise apost-mission/final accounting and completion of the transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment to the system).

Operation of Craft/Interaction with Management System

Referring to FIGS. 76 to 81C, according to an exemplary embodiment,processes for interaction by UAV/drone craft with a system formanagement/administration of airspace using data/data communications isshown schematically. According to an exemplary embodiment, the systemand craft/operator may in the initial interaction transact to registerthe craft to perform a planned mission in the airspace (e.g. transitthrough the airspace and/or on a delivery or route to a destination inthe airspace).

Operation of Craft—Feature (FIG. 76)

Referring to FIG. 76 according to an exemplary embodiment, a process forinteraction by UAV/drone craft operating in an airspace with a systemfor management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIG. 76 may be used for a UAV/drone craft under thedirection of an operator/remote pilot provided with the capability tomonitor/control the craft in real-time (and for dynamic transactionswith the system) and/or with and autonomous/on-board control function(e.g. with appropriate telemetry/data communications) intending toperform a proposed mission in the managed airspace, such as delivery ofa parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.) a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace).

Upon completion by the craft of the mission in the airspace the systemcompletes data collection and conducts data analysis (e.g. analysis ofdata collected during the mission and/or of data obtained from thecraft/operator and/or other sources during and/or after the mission) toprovide a post-mission corroboration/determination of use/access offlyway segments and zones/regions in the airspace by the craft (e.g.based on detected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace as detected/monitoredand reported) and application of the fee/rate to be assessed to thecraft for the detected/actual use/access to the airspace by the craftduring the mission. Communication/notice to the craft/operator maycomprise a post-mission/final accounting provided by the system to thecraft to complete the interaction/transaction between the system and thecraft/operator (e.g. with final/adjusted invoicing/billing of theappropriate amount due to the appropriate account for the craft/operatorfor payment).

Operation of Craft—Transmit Data/Post-Mission (FIG. 77)

Referring to FIG. 77 according to an exemplary embodiment, a process forinteraction by UAV/drone craft operating in an airspace with a systemfor management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIG. 77 may be used for a UAV/drone craft under thedirection of an operator/remote pilot provided with the capability tomonitor/control the craft in real-time (and for dynamic transactionswith the system) and/or with and autonomous/on-board control function(e.g. with appropriate telemetry/data communications) intending toperform a proposed mission in the managed airspace, such as delivery ofa parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.) a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed.

During the mission, data from tracking/monitoring (e.g. from detectorsand/or obtained from the craft/operator and/or from other sources) maybe used by the system for determination of adjustments of fee/rate to beassessed to the craft (e.g. based on detected/actual use of flywaysegments, time-weighted use of zones/regions, etc. by the craft in theairspace).

Upon completion by the craft of the mission in the airspace, data may betransmitted to the system from the craft/operator. The system completesdata collection and conducts data analysis (e.g. analysis of datacollected during the mission and/or of data obtained from thecraft/operator and/or other sources during and/or after the mission) toprovide a post-mission corroboration/determination of use/access offlyway segments and zones/regions in the airspace by the craft (e.g.based on detected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace as detected/monitoredand reported) and application of the fee/rate to be assessed to thecraft for the detected/actual use/access to the airspace by the craftduring the mission. Communication/notice to the craft/operator maycomprise a post-mission/final accounting provided by the system to thecraft to complete the interaction/transaction between the system and thecraft/operator (e.g. with final/adjusted invoicing/billing of theappropriate amount due to the appropriate account for the craft/operatorfor payment).

Operation of Craft—Transmit Data/Mission (FIGS. 78A and 78B)

Referring to FIGS. 78A and 78B according to an exemplary embodiment, aprocess for interaction by UAV/drone craft operating in an airspace witha system for management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIGS. 78A and 78B may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time (and for dynamictransactions with the system) and/or with and autonomous/on-boardcontrol function (e.g. with appropriate telemetry/data communications)intending to perform a proposed mission in the managed airspace, such asdelivery of a parcel/payload to a location in the airspace and/orpassage through the airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.) a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed; communication between the system and craft/operator ofdata/information (e.g. status, location, conditions, traffic, alerts,etc.) during the mission facilitates performance of the mission in theairspace by the craft and administration/management of the airspace bythe system.

During the mission, data from tracking/monitoring during the mission mayalso be transmitted between the system and the craft/operator. Asindicated, in FIG. 78B, during the mission, data fromtracking/monitoring (e.g. from detectors and/or obtained from thecraft/operator and/or from other sources) may be used by the system fordetermination of adjustments of fee/rate to be assessed to the craft(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace).

Upon completion by the craft of the mission in the airspace, data may betransmitted to the system from the craft/operator. The system completesdata collection and conducts data analysis (e.g. analysis of datacollected during the mission and/or of data obtained from thecraft/operator and/or other sources during and/or after the mission) toprovide a post-mission corroboration/determination of use/access offlyway segments and zones/regions in the airspace by the craft (e.g.based on detected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace as detected/monitoredand reported) and application of the fee/rate to be assessed to thecraft for the detected/actual use/access to the airspace by the craftduring the mission. Communication/notice to the craft/operator maycomprise a post-mission/final accounting provided by the system to thecraft to complete the interaction/transaction between the system and thecraft/operator (e.g. with final/adjusted invoicing/billing of theappropriate amount due to the appropriate account for the craft/operatorfor payment).

Operation of Craft—Modify Rights/Dynamic (FIG. 79)

Referring to FIG. 79 according to an exemplary embodiment, a process forinteraction by UAV/drone craft operating in an airspace with a systemfor management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIG. 79 may be used for a UAV/drone craft under thedirection of an operator/remote pilot provided with the capability tomonitor/control the craft in real-time and for dynamic transactions withthe system and/or with and autonomous/on-board control function (e.g.with appropriate telemetry/data communications) intending to perform aproposed mission in the managed airspace, such as delivery of aparcel/payload to a location in the airspace and/or passage through theairspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.) a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed; communication between the system and craft/operator ofdata/information (e.g. status, location, conditions, traffic, alerts,etc.) during the mission facilitates performance of the mission in theairspace by the craft and administration/management of the airspace bythe system.

During the mission, data from tracking/monitoring during the mission mayalso be communicated between the system and the craft/operator. Asindicated, the craft/operator in a dynamic transaction with the systemmay modify the rights of the craft in the airspace (e.g. by purchase orbid to upgrade or enhance rights or by refund to downgrade or traderights). Rights as modified will determine the priority/status of thecraft and rate/fee for the completion of the mission; rights/status anddata from tracking/monitoring (e.g. from detectors and/or obtained fromthe craft/operator and/or from other sources) may be used by the systemfor determination of adjustments of fee/rate to be assessed to the craft(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace).

Upon completion by the craft of the mission in the airspace, data may betransmitted to the system from the craft/operator. The system completesdata collection and conducts data analysis (e.g. analysis of datacollected during the mission and/or of data obtained from thecraft/operator and/or other sources during and/or after the mission) toprovide a post-mission corroboration/determination of use/access offlyway segments and zones/regions in the airspace by the craft (e.g.based on detected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace as detected/monitoredand reported) and application of the fee/rate to be assessed to thecraft for the detected/actual use/access to the airspace by the craftduring the mission. Communication/notice to the craft/operator maycomprise a post-mission/final accounting provided by the system to thecraft to complete the interaction/transaction between the system and thecraft/operator (e.g. with final/adjusted invoicing/billing of theappropriate amount due to the appropriate account for the craft/operatorfor payment).

Operation of Craft—Modify Route/Dynamic (FIG. 80)

Referring to FIG. 80 according to an exemplary embodiment, a process forinteraction by UAV/drone craft operating in an airspace with a systemfor management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIG. 80, may be used for a UAV/drone craft under thedirection of an operator/remote pilot provided with the capability tomonitor/control the craft in real-time and for dynamic transactions withthe system and/or with and autonomous/on-board control function (e.g.with appropriate telemetry/data communications) intending to perform aproposed mission in the managed airspace, such as delivery of aparcel/payload to a location in the airspace and/or passage through theairspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.), a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed; communication between the system and craft/operator ofdata/information (e.g. status, location, conditions, traffic, alerts,etc.) during the mission facilitates performance of the mission in theairspace by the craft and administration/management of the airspace bythe system.

During the mission, data from tracking/monitoring during the mission mayalso be communicated between the system and the craft/operator. Asindicated, the craft/operator in a dynamic transaction with the systemmay modify the route of the craft in the airspace (e.g. by purchase orbid to upgrade or enhance rights or by refund to downgrade or traderights). For example, the craft/operator may wish to modify itsoperations/route in order to perform an additional parcel pickup ordelivery, to cancel/reschedule a previously planned parcel pickup ordelivery, to perform additional imaging operations, etc. The route asmodified and rights of the craft will apply to determine rate/fee forthe completion of the mission; rights/status and data fromtracking/monitoring (e.g. from detectors and/or obtained from thecraft/operator and/or from other sources) may be used by the system fordetermination of adjustments of fee/rate to be assessed to the craft(e.g. based on detected/actual use of flyway segments, time-weighted useof zones/regions, etc. by the craft in the airspace).

Upon completion by the craft of the mission in the airspace, data may betransmitted to the system from the craft/operator. The system completesdata collection and conducts data analysis (e.g. analysis of datacollected during the mission and/or of data obtained from thecraft/operator and/or other sources during and/or after the mission) toprovide a post-mission corroboration/determination of use/access offlyway segments and zones/regions in the airspace by the craft (e.g.based on detected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace as detected/monitoredand reported) and application of the fee/rate to be assessed to thecraft for the detected/actual use/access to the airspace by the craftduring the mission. Communication/notice to the craft/operator maycomprise a post-mission/final accounting provided by the system to thecraft to complete the interaction/transaction between the system and thecraft/operator (e.g. with final/adjusted invoicing/billing of theappropriate amount due to the appropriate account for the craft/operatorfor payment).

Operation of Craft—Modify Rate/Rights/Route (FIGS. 81A to 81C)

Referring to FIGS. 81A to 81C according to an exemplary embodiment, aprocess for interaction by UAV/drone craft operating in an airspace witha system for management/administration of the airspace using data/datacommunications is shown schematically. The process indicatedschematically in FIGS. 81A to 81C may be used for a UAV/drone craftunder the direction of an operator/remote pilot provided with thecapability to monitor/control the craft in real-time and for dynamictransactions with the system and/or with and autonomous/on-board controlfunction (e.g. with appropriate telemetry/data communications) intendingto perform a proposed mission in the managed airspace, such as deliveryof a parcel/payload to a location in the airspace and/or passage throughthe airspace.

According to an exemplary embodiment, the system and craft/operator mayinitially transact (e.g. by purchase/sale, auction/bid, etc.) toregister the craft to the airspace to perform a planned mission in theairspace (e.g. transit through the airspace and/or on a delivery orroute to a destination in the airspace).

The craft (e.g. identity, profile/type, capability, account information,etc.) and the mission (e.g. destination/purpose, flight plan,time/priority, etc.) of the craft in the airspace each areregistered/evaluated by the system; rights (e.g. priority/statusrelative to other craft, for routing, etc.) a route (e.g. proposedflyway segments and zone/region access/use timing) and each are obtainedby the craft from the system for the mission in the airspace.

Registration of the craft and mission by the system informs the craftand the system of relevant conditions in the airspace (e.g.traffic/status, environmental conditions/weather, events/situations,potential obstructions/alerts, etc.) and facilitates a determination andapplication of appropriate license/rights and the proper fee/rate to beassessed to the craft/operator to perform the mission on an appropriateroute in the airspace; verification of the rights/route for the craftwith the system facilitates initiation by the craft/operator of themission in the airspace.

During the mission the craft is tracked and monitored (e.g.location/tracking, status, etc. by detectors and/or other datacommunication) as the craft is in transit/passage along theassigned/approved route with corresponding flyway segments andzones/regions in performance of the mission in the airspace; conditionsin the airspace (e.g. traffic/status, environmental conditions/weather,events/situations, potential obstructions/alerts, etc.) are monitoredand evaluated as the craft performs the mission in the airspace.

Tracking/monitoring by the system of the craft along the route andmonitoring/evaluation by the system of conditions in the airspace willcontinue until the mission to be performed by the craft in the airspaceis completed; communication between the system and craft/operator ofdata/information (e.g. status, location, conditions, traffic, alerts,etc.) during the mission facilitates performance of the mission in theairspace by the craft and administration/management of the airspace bythe system.

During the mission, data from tracking/monitoring during the mission mayalso be communicated between the system and the craft/operator. Asindicated, in FIGS. 81A-81C, in a dynamic transaction with the systemthe craft/operator may modify rights/priority of the craft and maymodify the route (e.g. flyway segments and zones/regions) of the craft.

The rights and route of the craft and data from tracking/monitoring(e.g. from detectors and/or obtained from the craft/operator and/or fromother sources) may be used by the system for determination ofadjustments of fee/rate to be assessed to the craft (e.g. based ondetected/actual use of flyway segments, time-weighted use ofzones/regions, etc. by the craft in the airspace). See FIG. 81A.According to an alternative embodiment shown schematically in FIG. 81B,the craft/operator in a dynamic transaction with the system candetermine whether to modify rights for the craft (e.g. in response totraffic/conditions/time, etc.); if rights of the craft are modified thenthe craft/operator may modify the route. According to an alternativeembodiment shown schematically in FIG. 81C, the craft/operator in adynamic transaction with the system modify rights/priority for the craftand determine whether to modify the route for the craft (e.g. inresponse to traffic/conditions/time, changes in parcel pickups ordeliveries, changes in mission operations, etc.). If the route is notmodified, the craft/operator may restore rights.

During the mission, upon completion by the craft of the mission in theairspace, data may be transmitted to the system from the craft/operator.The system completes data collection and conducts data analysis (e.g.analysis of data collected during the mission and/or of data obtainedfrom the craft/operator and/or other sources during and/or after themission) to provide a post-mission corroboration/determination ofuse/access of flyway segments and zones/regions in the airspace by thecraft (e.g. based on detected/actual use of flyway segments,time-weighted use of zones/regions, etc. by the craft in the airspace asdetected/monitored and reported) and application of the fee/rate to beassessed to the craft for the detected/actual use/access to the airspaceby the craft during the mission. Communication/notice to thecraft/operator may comprise a post-mission/final accounting provided bythe system to the craft to complete the interaction/transaction betweenthe system and the craft/operator (e.g. with final/adjustedinvoicing/billing of the appropriate amount due to the appropriateaccount for the craft/operator for payment).

Incorporation of Present Technology/Systems

The system and method according to exemplary and alternative embodimentsmay be configured to integrate or operate with present known (and/orfuture) systems and technology, for example, systems for integratingUAV/drone craft into existing air traffic management systems (e.g. U.S.Patent Application Publication No. 2013/014646 A1), systems forcommunicating the position of a UAS/aircraft with an air traffic controlreporting system/ground control station (e.g. U.S. Pat. No. 8,437,956),flight management systems for UAVs/drones through segregated andnon-segregated airspace with facilitated navigation functions such asusing guidance setpoints/commands or other data (e.g. U.S. Pat. Nos.8,515,593 and 8,521,340 and 8,543,255) systems providing tools andtechniques for computing flight plans incorporating trajectories (havingspatial and temporal dimensions) for UAVs and to route/reroute UAVstrajectories around obstacles as the UAVs visit destinations (e.g. U.S.Pat. Nos. 8,082,102 and 6,871,816), UAV systems for executing a missionplan (e.g. U.S. Pat. No. 8,600,602), systems for unmanned vehiclecontrol using X-Y-Z coordinates/coordination and a computing system(e.g. U.S. Pat. No. 8,577,535), systems for data communications with UAVcraft (e.g. U.S. Patent Application Publication No. 2012/0299751 andU.S. Pat. No. 7,231,294), systems using data/sensors and communicationsfor communicating location and mitigating risk of aircraft interactionsin an airspace (e.g. U.S. Pat. Nos. 8,437,956 and 8,368,584 and8,380,425) systems for managing flight parameters, terrain andconditions such as weather/wind and/or related communications/dataincluding to facilitate autonomy of UAVs (e.g. U.S. Pat. Nos. 8,355,834and 7,302,316) systems using transceivers/transponders (such asRFID/DSRC tags with commercial EZ-PASS™ technology for collection oftolls/fares) for vehicles (e.g. U.S. Pat. No. 5,819,234 and U.S. PatentApplication Publication No. 2011/0161140 (integrating systems withcamera/imaging data communications)), systems providing ground controlstations (with user interfaces) and telemetry/telecommand functions andremote/linked communications (such as by wireless data link) withUAVs/unmanned air vehicles (e.g. U.S. Patent Application Publication No.2007/0244608) systems for zone policy administration for management ofentities (such as vehicles) within zones incorporating association ofentities and sensors/objects as well as events and rules/policies forentities using data (e.g. U.S. Patent Application Publication No.2008/0072284). Such systems/technology and patent documents areincorporated by reference in the present application as background forthe present inventions.

* * *

It is important to note that the construction and arrangement of theelements of the inventions as described in system and method and asshown in the figures above is illustrative only. Although someembodiments of the present inventions have been described in detail inthis disclosure, those skilled in the art who review this disclosurewill readily appreciate that many modifications are possible withoutmaterially departing from the novel teachings and advantages of thesubject matter recited. Accordingly, all such modifications are intendedto be included within the scope of the present inventions. Othersubstitutions, modifications, changes and omissions may be made in thedesign, variations in the arrangement or sequence of process/methodsteps, operating conditions and arrangement of the preferred and otherexemplary embodiments without departing from the spirit of the presentinventions.

It is important to note that the system and method of the presentinventions can comprise conventional technology (e.g. computing systems,telecommunication systems, networking technology, data storage, datatransmission, data/file structures/formats, systems/software,application programs, mobile device technology, etc.) or any otherapplicable technology (present or future) that has the capability toperform the functions and processes/operations indicated in the FIGURES.All such technology is considered to be within the scope of the presentinventions.

The invention claimed is:
 1. A system for managing an airspacecomprising a plurality of flyway segments for unmanned aircraftcomprising: (a) a computing system configured (1) for administrating theairspace and aircraft and (2) for directing aircraft in the airspace;(b) a monitoring system configured to monitor conditions in theairspace; wherein the computing system is connected to data sources toprovide data for administrating and directing aircraft in the airspace;wherein administrating the airspace comprises designation of a set ofzones comprising a set of flyway segments in the airspace for operationof aircraft, and wherein administrating aircraft further comprisesregistration of aircraft to operate in the airspace, whereinregistration of an aircraft comprises a license providing rights to theaircraft at a variable rate based on at least one selected factor. 2.The system of claim 1 wherein directing aircraft comprises assigning aroute to the aircraft to operate in the airspace.
 3. The system of claim1 wherein conditions comprise at least one of environmental conditionsin the airspace and aircraft traffic in the airspace.
 4. The system ofclaim 1 wherein data sources comprise at least one of data sources inthe airspace and data sources from a network.
 5. The system of claim 1wherein administrating the airspace comprises establishing rules foraircraft operation.
 6. The system of claim 1 wherein the licenseprovides a right to operate within a specified zone or flyway segment.7. The system of claim 1 wherein the license provides a right to operatewithin a specified zone or flyway segment during a specified timeinterval or for a specified duration.
 8. The system of claim 1 whereinthe license provides an exclusive right to operate within a specifiedzone or flyway segment during a specified time interval or for aspecified duration.
 9. The system of claim 1 wherein the licenseprovides a right to operate specified equipment.
 10. The system of claim1 wherein the license provides a right to land on a surface in theairspace.
 11. The system of claim 10 wherein the right to land comprisesthe right to land at a site in the airspace.
 12. The system of claim 11wherein the site comprises on the ground, on a building, on a power lineand on a vehicle.
 13. The system of claim 1 wherein the license providesa right to take off from a site within the airspace.
 14. The system ofclaim 1 wherein the license provides a right to deliver payload to asite within the airspace.
 15. The system of claim 1 wherein the licenseprovides a specified occupancy space for the aircraft.
 16. A system formanaging an airspace comprising a plurality of flyway segments and atleast one zone for unmanned aircraft comprising: (a) a computing systemconfigured (1) for administrating the airspace and aircraft and (2) fordirecting aircraft in the airspace; (b) a monitoring system configuredfor monitoring of conditions in the airspace; wherein administratingaircraft comprises registration of aircraft to operate in the airspaceand at least one transaction with an aircraft, and wherein the aircraftcan complete a segment of a mission to be performed by the aircraft inthe airspace and conduct a transaction to be charged for use of theairspace at a rate that is variable according to at least one selectedfactor.
 17. The system for claim 16 wherein directing aircraft comprisesassigning a route to the aircraft to operate in the airspace.
 18. Thesystem for claim 16 wherein monitoring of conditions comprises at leastthe steps of monitoring environmental conditions in the airspace andaircraft traffic in the airspace.
 19. The system for claim 16 whereinthe computing system is connected to data sources to provide data foradministration and direction of aircraft.
 20. The system for claim 16wherein administrating the airspace comprises designation of a set ofzones comprising a set of flyway segments in the airspace for operationof aircraft.
 21. The system for claim 16 wherein conditions comprise atleast one of weather conditions in the airspace and aircraft trafficcount in the airspace.
 22. The system for claim 19 wherein data sourcescomprise at least one of data sources in the airspace and data sourcesfrom a network.
 23. The system for claim 16 wherein a transactioncomprises a grant of license providing rights to the aircraft foroperation in the airspace at a rate.
 24. The system for claim 16 whereinconditions comprise the number of other aircraft present in the region.25. The system of claim 16 wherein a transaction for the collection ofpayment is at completion of the mission.
 26. The system of claim 23wherein the rate comprises a function of at least one of the number ofaircraft, the density of aircraft in the region, and the separationbetween aircraft, wherein the rate is higher for exclusive occupancy ofa flyway segment.
 27. The system for claim 23 wherein if occupancyconditions change during time the rate can be time weighted.
 28. Thesystem of claim 16 wherein registering an aircraft comprises a licenseproviding rights to the aircraft.
 29. The system of claim 16 wherein aprofile comprises data for the aircraft.
 30. The system for claim 16wherein the aircraft is in operation on a mission in the airspace underlicense.
 31. The system of claim 16 wherein registering aircraftcomprises a transaction to issue a license with a rate for use of theairspace.
 32. The system of claim 16 wherein the aircraft may buy rightsto a zone.
 33. The system of claim 16 wherein the aircraft may licenserights to a zone.
 34. The system of claim 16 wherein the aircraft isauthorized to initiate a mission upon obtaining rights by license forthe airspace.
 35. A system for managing an airspace comprising aplurality of flyway segments and at least one zone for unmanned aircraftcomprising: (a) a computing system configured (1) for administrating theairspace and aircraft and (2) for directing aircraft in the airspace;(b) a monitoring system configured for monitoring of conditions in theairspace; wherein administrating aircraft comprises registration ofaircraft to operate in the airspace and at least one transaction with anaircraft, and wherein a profile for an aircraft comprises at least oneof aircraft type and aircraft capability.
 36. The system for claim 35wherein directing aircraft comprises assigning a route to the aircraftto operate in the airspace.
 37. The system for claim 35 whereinmonitoring of conditions comprises at least the steps of monitoringenvironmental conditions in the airspace and aircraft traffic in theairspace.
 38. The system for claim 35 wherein the aircraft can completea segment of a mission to be performed by the aircraft in the airspaceand conduct a transaction to be charged for use of the airspace at arate.
 39. The system for claim 35 wherein the computing system isconnected to data sources to provide data for administration anddirection of aircraft.
 40. The system for claim 35 whereinadministrating the airspace comprises designation of a set of zonescomprising a set of flyway segments in the airspace for operation ofaircraft.
 41. The system for claim 35 wherein conditions comprise atleast one of weather conditions in the airspace and aircraft trafficcount in the airspace.
 42. The system for claim 39 wherein data sourcescomprise at least one of data sources in the airspace and data sourcesfrom a network.
 43. The system for claim 35 wherein a transactioncomprises a grant of license providing rights to the aircraft foroperation in the airspace at a rate.
 44. The system for claim 35 whereinconditions comprise the number of other aircraft present in the region.45. The system of claim 35 wherein a transaction for the collection ofpayment is at completion of the mission.
 46. The system of claim 43wherein the rate comprises a function of at least one of the number ofaircraft, the density of aircraft in the region, and the separationbetween aircraft, wherein the rate is higher for exclusive occupancy ofa flyway segment.
 47. The system for claim 43 wherein if occupancyconditions change during time the rate can be time weighted.
 48. Thesystem of claim 35 wherein registering an aircraft comprises a licenseproviding rights to the aircraft.
 49. The system of claim 35 wherein aprofile comprises data for the aircraft.
 50. The system for claim 35wherein the aircraft is in operation on a mission in the airspace underlicense.
 51. The system of claim 35 wherein registering aircraftcomprises a transaction to issue a license with a rate for use of theairspace.
 52. The system of claim 35 wherein the aircraft may buy rightsto a zone.
 53. The system of claim 35 wherein the aircraft may licenserights to a zone.
 54. The system of claim 35 wherein the aircraft isauthorized to initiate a mission upon obtaining rights by license forthe airspace.
 55. The system of claim 35 wherein the aircraft comprisesa system for dynamic transactions with the management system.
 56. Asystem for managing an airspace comprising a plurality of flywaysegments and at least one zone for unmanned aircraft comprising: (a) acomputing system configured (1) for administrating the airspace andaircraft and (2) for directing aircraft in the airspace; (b) amonitoring system configured for monitoring of conditions in theairspace; wherein administrating aircraft comprises registration ofaircraft to operate in the airspace and at least one transaction with anaircraft, and wherein the aircraft comprises a system for dynamictransactions with the management system that occur when the craft is inoperation in the airspace.
 57. The system for claim 56 wherein directingaircraft comprises assigning a route to the aircraft to operate in theairspace.
 58. The system for claim 56 wherein monitoring of conditionscomprises at least the steps of monitoring environmental conditions inthe airspace and aircraft traffic in the airspace.
 59. The system forclaim 56 wherein the aircraft can complete a segment of a mission to beperformed by the aircraft in the airspace and conduct a transaction tobe charged for use of the airspace at a rate.
 60. The system for claim56 wherein the computing system is connected to data sources to providedata for administration and direction of aircraft.
 61. The system forclaim 56 wherein administrating the airspace comprises designation of aset of zones comprising a set of flyway segments in the airspace foroperation of aircraft.
 62. The system for claim 56 wherein conditionscomprise at least one of weather conditions in the airspace and aircrafttraffic count in the airspace.
 63. The system for claim 60 wherein datasources comprise at least one of data sources in the airspace and datasources from a network.
 64. The system for claim 56 wherein atransaction comprises a grant of license providing rights to theaircraft for operation in the airspace at a rate.
 65. The system forclaim 56 wherein conditions comprise the number of other aircraftpresent in the region.
 66. The system of claim 56 wherein a transactionfor the collection of payment is at completion of the mission.
 67. Thesystem of claim 64 wherein the rate comprises a function of at least oneof the number of aircraft, the density of aircraft in the region, andthe separation between aircraft, wherein the rate is higher forexclusive occupancy of a flyway segment.
 68. The system for claim 64wherein if occupancy conditions change during time the rate can be timeweighted.
 69. The system of claim 56 wherein registering an aircraftcomprises a license providing rights to the aircraft.
 70. The system ofclaim 56 wherein a profile comprises data for the aircraft.
 71. Thesystem for claim 56 wherein the aircraft is in operation on a mission inthe airspace under license.
 72. The system of claim 56 whereinregistering aircraft comprises a transaction to issue a license with arate for use of the airspace.
 73. The system of claim 56 wherein aprofile for an aircraft comprises at least one of aircraft type andaircraft capability.
 74. The system of claim 56 wherein the aircraft maybuy rights to a zone.
 75. The system of claim 56 wherein the aircraftmay license rights to a zone.
 76. The system of claim 56 wherein theaircraft is authorized to initiate a mission upon obtaining rights bylicense for the airspace.